Skip to content

EQUIRE developer guide

Connect agents to governed deal intelligence.

EQUIRE offers an OAuth-protected Model Context Protocol connector for approved organizations. It makes source-grounded deal work available to external assistants without bypassing access controls, review gates, or team judgment.

Start with discovery

Use the published contract before sending a connector request.

The machine-readable OpenAPI description documents the EQUIRE Agent API. The API catalog links the OpenAPI contract, this guide, and the connector service. The MCP server card lists the actual authenticated tool inventory and required scopes. Agents should first discover OAuth metadata, register a client, and request the least-privilege scopes required for the workflow.

The production connector endpoint is /mcp. It uses OAuth authorization code plus PKCE, exposes protected-resource metadata at /.well-known/oauth-protected-resource, and publishes authorization-server metadata at /.well-known/oauth-authorization-server. The connector is available only when an organization has enabled and authorized it.

Requests are rate-limited per authorized user and organization. Clients should honor standard RateLimit policy headers and Retry-After when a request receives HTTP 429. EQUIRE returns structured JSON errors and bearer challenges rather than HTML errors on connector routes.

The connector authentication guide specifies the implemented PKCE, dynamic-client registration, grant, token-rotation, scope, and disconnect behavior. It is a public guide to an authenticated service, not a claim that EQUIRE offers anonymous self-service access.

Scopes

Request only the access a task needs.

Read scopes provide source-grounded data within the caller's organization and existing permissions. Write scopes remain governed: they support notes, diligence work, listing workflows, or staged changes, never automatic approval, release, IC decision, destructive cleanup, or unrestricted document export.

  • deals:read · documents:search · valuation:read · diligence:read
  • prospects:read · firm_memory:read · listings:read
  • deal_notes:write · diligence:write · listings:write · actions:stage

For a product-level walkthrough before connecting an account, use the read-only example deal. For platform and workflow detail, use the public documentation and agent guide.