ADAPTERS
Narrow, audited bindings into the systems your enterprise already runs.
AgentAnywhere agents are most valuable when they can act inside your systems of record. Adapters are how they do it — explicit read/write surfaces, declared at deployment, enforced by the runtime, versioned in Registry. Workday, SAP, Salesforce, ServiceNow at launch; the SDK is the path for everything else.
Connectivity is a contract, not a setting.
Most enterprise integration platforms ship hundreds of connectors and treat the surface area as a feature. AgentAnywhere ships four launch adapters and treats the surface area as a contract.
Each adapter declares, at deployment time, every table it can read from and every action it can take. The list is enforced by the runtime, not by the adapter's own self-restraint. A `Salesforce` adapter that is configured to read accounts and write notes cannot, at runtime, write opportunities — the runtime refuses the call before it reaches Salesforce.
Adapters are versioned in Registry alongside the agents that use them. A new adapter version is a new registry entry, with its own approval and rollback. No adapter ever silently changes its surface in a deployed customer environment.
Launch adapters.
Each launch adapter ships with a tested deployment topology, a default read/write surface that customers refine, and integration tests against the vendor's reference environment. Custom adapters follow the same SDK pattern; most are shipped within four to six weeks of pilot kickoff.
Workday
Read employee data, organizational hierarchy, position metadata. Write structured records into approved modules under change-managed permissions. Designed to integrate cleanly with TalentAnywhere for talent and learning workflows.
SAP
Read master data, transactional data, and module-specific entities. Write transactions through the change-management surface your SAP team owns. SAP S/4HANA and ECC supported; BW/4HANA on the roadmap.
Salesforce
Read accounts, opportunities, contacts, custom objects. Write notes, tasks, and activities. Drives the Marketing Agent and RFP Agent against your existing pipeline. Sandbox-first deployment pattern.
ServiceNow
Read incidents, changes, problems, configuration items. File and update tickets with structured payloads. Drives the SDLC Agent and Cloud Optimizer against your existing ITSM workflow.
Surface area, made explicit.
Every adapter you deploy comes with an explicit declaration of what it can read and what it can write. Two artifacts ship with every adapter version: the surface manifest and the runtime enforcement.
Surface manifest
A signed manifest, stored in Registry, lists every table and every action the adapter is permitted to touch in your environment.
Your security team reviews the manifest before promotion. Promotion requires the manifest's signature; the runtime refuses to load an adapter whose manifest signature does not match.
The manifest is human-readable. No buried YAML, no opaque protobuf, no "trust the vendor" model.
Runtime enforcement
The agent runtime sits between every agent and every adapter call. Calls outside the manifest are rejected before they reach the adapter binary, with a typed error that lands in the run trace.
Rejected calls are observable in Observe and reportable in the audit trail. They are not silent failures.
Adapter upgrades that expand the surface require a new manifest, a new approval, and a new promotion event. The expansion is auditable.
Custom adapters: same SDK, same governance.
Most enterprises run on more than the four launch systems. We do not ship a hundred half-tested adapters to make the matrix look full. We ship the SDK and the deployment pattern for building the one adapter you actually need.
Custom adapters follow the same surface-manifest and runtime-enforcement pattern as the launch adapters. Your engineering team builds the binding; your security team reviews the manifest; your governance team approves promotion through Registry. The result is an adapter your team owns, your team can audit, and your team can update without waiting for our roadmap.
Most custom adapters ship within four to six weeks of a pilot kickoff. Solutions Architecture pairs with the customer engineering team for the duration.
Pilot a custom adapter on your stack.
Pilots scope to one custom adapter, one named system of record, four to six weeks. Our solutions architects pair with your engineering team; the adapter ships into your sovereign environment with a signed surface manifest and full Registry governance from day one.