Corgent API Surface¶
Last updated: 2026-06-28
Corgent is Cortensor's agentic trust and execution surface. It packages router primitives such as delegate, validate, factcheck, and arbitration workflows into calls that agents and protocols can use before executing or trusting work.
Core Primitives¶
| Primitive | Purpose | Route or product relationship |
|---|---|---|
| Delegate | Send work to Cortensor under an explicit policy. | Router endpoints:POST /api/v1/delegatePOST /api/v2/delegatePOST /api/v3/delegate |
| Validate | Check a result, claim, or proposed action before relying on it. | Router endpoints:POST /api/v1/validatePOST /api/v2/validatePOST /api/v3/validate |
| Factcheck | Validate factual claims, optionally with realtime evidence. | Router endpoints:POST /api/v1/factcheckPOST /api/v1/fact-check |
| Arbitrate | Escalate disputed outputs to a stronger verification policy. | Product workflow that requires published policy, evidence handling, and legal terms before binding-use claims. |
Route Families¶
| Family | Current route family |
|---|---|
| Delegate | Core: POST /api/v1/delegate, POST /api/v2/delegate, POST /api/v3/delegate.Trial: POST /api/v1/trial/delegate, POST /api/v2/trial/delegate.x402: POST /api/v1/x402/delegate, POST /api/v2/x402/delegate. |
| Validate | Core: POST /api/v1/validate, POST /api/v2/validate, POST /api/v3/validate.Trial: POST /api/v1/trial/validate, POST /api/v2/trial/validate.x402: POST /api/v1/x402/validate, POST /api/v2/x402/validate. |
| Factcheck | Core: POST /api/v1/factcheck, POST /api/v1/fact-check.Trial: POST /api/v1/trial/factcheck, POST /api/v1/trial/fact-check.x402: POST /api/v1/x402/factcheck, POST /api/v1/x402/fact-check. |
| Agent protocols | GET /.well-known/agent.json, GET /api/v1/a2a/agent.json, GET /api/v1/a2a/discovery; MCP transport can advertise or expose these capabilities where enabled. |
Implementation Layers¶
| Layer | Documentation focus |
|---|---|
| Router primitives | Route behavior, session selection, redundancy, timeout, and verdict shape. |
| Portal/gateway access | Whether hosted keys can call delegate/validate/factcheck, and which model/session pools are mapped. |
| Corgent service wrapper | Product API, authentication, policy presets, evidence format, and dashboard/logging path. |
| ERC-8004 registration | Registration, discovery, agent metadata, and proof artifacts when active. |
| Arbitration/dispute workflows | Escalation policy, evidence retention, reviewer path, and legal/product boundary. |
Agent Flow¶
sequenceDiagram
participant Agent as Agent
participant Corgent as Corgent
participant Router as Router
participant Network as Cortensor sessions
Agent->>Corgent: delegate or validate request
Corgent->>Router: route with policy and session pool
Router->>Network: task lifecycle
Network-->>Router: result, verdict, or evidence
Router-->>Corgent: normalized response
Corgent-->>Agent: action result or trust decision
See Router Node for router mechanics and Corgent And Bardiel for product positioning.