Core as Infrastructure

Use Isomer Core directly via API or MCP to power your own AI agents with Isomer's ingestion, ontology, and claim graph.

Isomer Core is available as infrastructure for teams building their own AI agents. If you have existing detection or workflow logic you want to keep, you can consume Core directly — same ingestion pipeline, same ACORD-aligned ontology, same claim graph, same security posture — without using Signals or Actions.

What you get

Access methods

Core exposes two access methods.

API

HTTP endpoints for programmatic access from any language or system. Use the API to query the claim graph, retrieve documents, resolve parties, and search — by identity or natural language.

# Retrieve a claim
curl https://api-<your-tenant>.isomer.ai/v1/claims/{claimId} \
  -H "Authorization: Bearer {access_token}"

# Semantic search across claims
curl -X POST https://api-<your-tenant>.isomer.ai/v1/claims/semantic-search \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{"query": "rear-end collision with deferred medical treatment", "limit": 20}'

See the API reference for the full surface — authentication, ingestion, claims, events & parties, and documents & files.

MCP

Model Context Protocol is the canonical way to wire an external AI agent into Core. Isomer runs a remote, hosted MCP server that exposes Core's capabilities as tools — your agent calls them directly, and the protocol handles auth and schemas.

There's nothing to install. Point an MCP client at your tenant endpoint over the Streamable HTTP transport:

{
  "mcpServers": {
    "isomer": {
      "type": "http",
      "url": "https://api-<your-tenant>.isomer.ai/mcp"
    }
  }
}

Connections authenticate over OAuth 2.1 — most modern clients discover and complete the flow automatically. Available tools mirror the Core API: get_claim, search_claims, list_documents, get_claim_neighborhood, and more. See the MCP overview, connecting, and the full tool reference.

Authentication

Both access methods use OAuth 2.0 access tokens scoped to your tenant. Credentials are provisioned per integration — contact your Isomer team to get set up. See API authentication for details.

Access tokens are scoped and time-limited. Isomer does not store persistent service-account credentials — see Security for details.

When to use Core directly

Core as infrastructure is designed for teams that:

• Have existing detection models or rules they want to run on structured claim data
• Are building AI agents in-house and want Isomer's ingestion and ontology without adopting Signals or Actions
• Need programmatic access to the claim graph for custom reporting, integrations, or downstream systems

If you want pre-built risk detection, use Signals. If you want pre-built workflow execution, use Actions. Core is the right choice when you're bringing your own logic.

Next steps