AI Agentic Framework — integration surface

This host serves the platform API. The operator console is a separate host.

What a Domain owner builds

Exactly one artifact: a Domain Adapter — an HTTPS service implementing five endpoints, authenticated with a shared x-api-key header. The kernel never branches on your domain's vocabulary; everything specific to your vertical lives behind this seam.

Endpoint	Purpose
`POST /{v}/tools/execute`	Execute a domain tool call
`POST /{v}/context/resolve`	Cold-start durable context for a contact
`POST /{v}/prerequisite/run`	Materialise an evaluation prerequisite
`POST /{v}/partner/provision`	Create domain resources for a new partner
`POST /{v}/partner/deprovision`	Tear them down

Registering your Domain

Your adapter's base URL is Domain data, not deployment configuration — you supply it at onboarding:

POST /account/v1/domains
{
  "name": "Your organisation",
  "industry": "general",
  "domainAdapterBaseUrl": "https://adapter.example.com/your-domain"
}

The base URL carries your own path prefix: the kernel appends only /v1/context/resolve, /v1/tools/execute and so on. A new Domain is seeded with the platform's base user-context structure, which you then own and can edit.

API prefixes on this host

Prefix	Service
`/account/v1/*`	Accounts, Domains, Partners, configuration
`/agent-manifest/v1/*`	Agents, rules, intents, tools, golden cases
`/dialogue/v1/*`	Conversations and session state
`/mcp/v1/*`	Tool gateway
`/evaluator/v1/`, `/optimizer/`	Evaluation and optimisation
`/actor/v1/*`	Persona simulation
`/conversation/v1/*`	Conversation runtime

Full contracts are in the platform specification. Contact the platform operator for credentials.