Agent API v1 Reference

v1 (/v1/*) is the current stable surface and remains fully supported. v2 is additive; nothing in v1 is removed by this documentation.

Base URL: https://agent-api.degov.ai

Authentication

• Free endpoints: /v1/meta/pricing, /v1/daos.
• Paid endpoints: x402 payment or partner token (x-degov-api-token) with scopes v1:paid:standard, v1:paid:plus, v1:paid:*.
• Internal first-party access uses a separate token and is not public.

Endpoints

Free

Method	Path	Usage
GET	/v1/meta/pricing	Discover x402 pricing before paid calls.
GET	/v1/daos	Discover covered DAOs and freshness metadata.

Paid — standard tier

Method	Path	Usage
GET	/v1/activity	Recent cross-DAO activity for agent summarization and monitoring.
GET	/v1/governance-events	Event-window governance activity for timeline analysis and alerting. Requires start_ms and end_ms.
GET	/v1/governance-signals	Curated governance signals.
GET	/v1/proposals/lookup	Resolve a proposal from partial identifiers (URL, title, external id).
GET	/v1/system/freshness	Overall ingestion freshness and dataset state.

Paid — plus tier

Method	Path	Usage
GET	/v1/daos/:daoId/brief	Compact DAO summary plus recent activity.
GET	/v1/daos/:daoId/proposals/:source/:externalId/evidence	Evidence-rich proposal detail for citation-heavy tasks.
GET	/v1/items/:kind/:externalId	One detailed normalized item by kind (proposal or forum_topic) and external id.

Response envelope

{
  "request": {},
  "freshness": { "generatedAt": "...", "dataAsOf": "...", "cacheStatus": "fresh" },
  "data": {}
}

cacheStatus ∈ memory_cache | fresh | cached_live | refreshed_live | registry_only.

Differences from v2

• v1 clamps out-of-range parameters; v2 rejects them (VALIDATION_ERROR).
• v1 uses start_ms/end_ms epoch-millisecond query parameters; v2 uses RFC 3339 from/to.
• v1 pagination/total semantics are legacy; v2 uses cursor pagination with no totals.
• v1 addresses items by kind + externalId; v2 uses opaque proposalKey/topicKey.

See Migration Guide for the endpoint-by-endpoint mapping.