OpenAPI
The machine-readable REST contract, including OAuth, request fields, idempotency, response envelopes, errors, and versioning.
Read Candor OpenAPICandor developer resources
Candor publishes a REST API, an authenticated remote MCP server, a command-line app, and standard Agent Skills. These surfaces share one contract: JSON is canonical, financial reads carry freshness and evidence, writes are idempotent, and every public operation records why it happened.
Access uses OAuth 2.0 with PKCE and scoped credentials. There are no static API keys to copy into a prompt. A user creates their own Candor account, then explicitly approves the agent or CLI that will use it.
The machine-readable REST contract, including OAuth, request fields, idempotency, response envelopes, errors, and versioning.
Read Candor OpenAPIThe production Streamable HTTP MCP endpoint. It uses OAuth and exposes the same guarded Candor operations through agent-native tools.
Connect to Candor MCPThe public getting-started skill explains when Candor fits, how to install the right package, and how an agent verifies access.
Read the setup skillThe source-available Candor Finance package contains the skill and platform manifests used by supported agent runtimes.
Open the package repositoryWhat Candor does on its own, how it recovers from failure, and what every agent is allowed to do.
Candor reviews each workspace on its own soon after its first transactions arrive, then again on a schedule. Nobody has to open a chat for that to happen.
Failures surface as data the agent can act on, and background work retries itself.
next_actions.Idempotency-Key, which the CLI and MCP server send for you, so a retried request cannot apply twice.{
"status": "error",
"errors": [{
"code": "insufficient_scope",
"retryable": false,
"required_capability": "candor:state.write",
"message":
"This OAuth grant requires the candor:state.write scope for this operation.",
"suggested_command": "candor auth login"
}],
"next_actions": [{
"intent": "reauthorize_oauth_client",
"command": "auth.login",
"shell": "candor auth login"
}]
}Agents work under scoped OAuth grants, and every operation leaves a record.
Candor exposes the same operations over every surface and works with the agent the user already has.
Each step is recorded in the activity history with the agent's reason.
Read the OpenAPI document first. Complete OAuth through the supported Candor setup flow, then call the versioned endpoint you need with a concise reason. POST operations require a stable Idempotency-Key so a retry cannot duplicate a logical write.
GET https://api.candor.money/v1/status Authorization: Bearer <access-token> X-Candor-Reason: Check workspace readiness
Public REST routes are versioned under /v1. Backward-compatible fields may be added within that version. A breaking contract moves to a new version. If a published operation is retired, Candor documents the replacement and timeline and sends the standard Deprecation and Sunset response headers before removal.
Production accounts are real financial workspaces; Candor does not advertise a public sandbox that could be mistaken for one. Use the published schemas and a user-controlled test account for integration development, without real credentials or raw financial data.
For the complete installation decision tree, start at START.md. For implementation questions that do not include private financial data, email support@candor.money.