AboutAPI

ACCORD FOR AGENTS

Research deeply.
Decide clearly.

Give any agent one research layer for evidence-backed answers, implementation planning, and independently verified code review.

Remote MCP Accord API key Sources included

SETUP

Connect in three steps

  1. 1

    Add the MCP server

    Open your agent's MCP settings and add the connection shown here.

  2. 2

    Add a key

    Use an accord_… key created by the account owner.

  3. 3

    Ask normally

    Send any question. Accord handles research and synthesis internally.

MCP CONNECTION
URL
https://askaccord.com/api/mcp

HEADER
Authorization: Bearer <YOUR_KEY>

The key is configured by the owner. The agent cannot create an account or issue itself credentials.

WHAT THE AGENT CAN DO

Research first. Review before merge.

ask_accord

Research questions and engineering plans

Four systems investigate independently, then Accord resolves the evidence into one answer or implementation plan. Supply relevant files for repository-grounded planning.

RETURNS answer · sources · usage
Request and response example
REQUEST
ask_accord({
  "query": "Research this architecture and produce a risk-ranked implementation plan.",
  "context": [{ "path": "docs/architecture.md", "content": "…" }],
  "strategy": "accord"
})
RESPONSE
{
  "answer": "The main risk is…",
  "sources": [{ "title": "…", "url": "https://…" }],
  "artifacts": [],
  "usage": { "inputTokens": 1840, "outputTokens": 920, "costMicros": 18400 }
}

review_code

Independent review with adjudication

Specialized reviewers examine correctness, security, tests, and operational risk. A final verifier rejects unsupported claims and merges duplicate findings. Your coding agent supplies the diff and relevant context; Accord does not clone the repository.

RETURNS verdict · verified findings · file and line
Request and response example
REQUEST
review_code({
  "task": "Review the current change before merge",
  "diff": "<git diff collected by the coding agent>",
  "focus": ["correctness", "security", "tests"]
})
RESPONSE
{
  "verdict": "changes_requested",
  "confidence": 0.94,
  "summary": "One verified defect needs attention.",
  "usage": { "inputTokens": 9100, "outputTokens": 2100, "costMicros": 92000 },
  "findings": [{
    "path": "lib/access.ts",
    "line": 42,
    "severity": "high",
    "title": "Authorization check can be bypassed",
    "explanation": "…",
    "suggestedFix": "…"
  }]
}

ACCESS

One account. One key.

Subscribe to Accord, create an API key, and use included usage across every model. Card overages remain optional and capped by the account owner.

AVAILABLE

Accord API key

The owner subscribes and creates an accord_… key. Included usage is used first; optional overages are charged to the saved card up to the owner's monthly cap.

See plans
COMING LATER

Pay per request

Accountless x402 payment is planned for autonomous agents that need to pay per request in USDC. It is not required for normal API access.

Payment availability for agent runtimes

LOW-LEVEL API

Building without MCP?

Use the answer endpoint for research and planning, and the review endpoint for an evidence-based verdict on a supplied change. Answer streaming is optional; the low-level review endpoint always returns NDJSON.

OpenAPI specificationGET /api/v1/openapiModel catalogGET /api/v1/models
Research and planningPOST /api/v1/answer
Security and code reviewPOST /api/v1/reviews
x402 consensusPOST /api/x402/consensus
x402 code reviewPOST /api/x402/reviews