For developers and authorized AI agents

A narrow, inspectable contract—without imaginary capabilities.

CoverIntent publishes one canonical registry for the public site, REST description, and agent-facing adapters. The current contract can describe the service and accept a consent-bound early-access request. It cannot quote, match, recommend, bind, pay, or transfer a lead.

Open capability registry Read OpenAPI

What is live now

A person or licensed-agent prospect can submit one consent-bound, email-only validation-interest request and receive a non-secret confirmation code. The code confirms intake only and is never an access token. No quote, recommendation, policy transaction, insurer match, or lead transfer is live.

Public discovery

Start by reading what is actually available.

Discovery is public. An agent should inspect the capability registry and user-facing boundary before proposing an action or collecting any data.

SurfaceMethodRoutePurpose

Canonical capability registryGET/api/capabilitiesSource for human and machine capability claims

OpenAPI 3.1.2GET/openapi.jsonREST discovery and email-only intake contract

Agent cardGET/.well-known/agent-card.jsonA2A 1.0 discovery metadata

LLM-readable summaryGET/llms.txtInformational llms.txt proposal format

Capability truth

Every effect carries a status.

Protocol availability does not imply insurance transaction authority. An adapter may expose the same narrow operation in a different envelope; it does not expand what the operation can do.

Read validation capabilities

available

Returns the exact CoverIntent CX1 truth boundary, accepted data contract, and supported discovery transports.

Effect: read_only
Transports: /api/capabilities · /openapi.json · /.well-known/agent-card.json · /api/a2a · /api/mcp

Submit validation interest

available

Accepts a minimum-necessary, consent-bound, email-only consumer or licensed-agent interest request. It does not request a quote or trigger insurer contact, lead transfer, a phone call, or a text message.

Effect: founder_tenant_interest_write
Transports: /api/interest · /api/a2a · /api/mcp

One intake contract

Ask for less. State the effect.

The same validated object powers the human form and protocol adapters. Consent is required. Unknown fields and sensitive insurance application data are rejected.

Email, state, line, timing, priority
Optional name and partner organization
Explicit research and early-access consent
No phone number or outreach authorization

In CX1, protocol clients assert the consent field in their payload. CoverIntent does not cryptographically authenticate a person’s delegation to an AI agent in this validation.

Validation-stage REST examplePOST /api/interest

{
  "role": "consumer",
  "email": "person@example.com",
  "state": "NV",
  "line": "renters",
  "timeframe": "one_to_three_months",
  "priority": "privacy_control",
  "consent": true
}

A success confirmation acknowledges founder research intake only. It is not an insurance application, Intent Grant, lead handoff, quote, or evidence of coverage.

Adapter discipline

REST, A2A, and MCP share one boundary.

Agent protocols are compatibility surfaces. They neither create authority on behalf of a person nor turn research intake into an insurance transaction. Consent is payload-asserted in CX1, not an authenticated delegation credential.

REST / OpenAPI

Direct inspection

Use the OpenAPI document to understand validation, effects, and response semantics.

Open specification

A2A 1.0

Agent message adapter

The validation adapter supports only the operations declared in the public agent card.

Open agent card

MCP 2026-07-28

Tool adapter

Tool discovery and calls remain bound to the same read-only discovery and narrow intake effects.

POST /api/mcp

Building on this?

Do not infer a capability that is absent from the registry.

If your use case requires quoting, carrier matching, applications, payment, binding, lead distribution, or consumer outreach, this validation service is not an eligible execution path.

Read the target model