Fletch
Docs

For agents

Fetch relevant chain facts on demand and preserve their provenance, timestamp and coverage.

Last verified against production: . See current limits and availability.

Connect the interface you use

A small retrieval loop

  1. Read /api/v1/status when freshness matters. HTTP 200 means the status request succeeded; inspect its verdict, jobs, timestamps and checkpoints.
  2. Resolve a known address through /api/v1/tokens/{address}, or narrow a listed-asset lookup by symbol. Search pools only when the task needs market data. Keep only the fields relevant to the user's task.
  3. Carry the chain ID, address, trust verdict and observation times alongside a number. Preserve nulls and partial-coverage markers. Fetch a specific historical endpoint for a historical question.
  4. Honor ETag and If-None-Match. A 304 has no JSON body; reuse the previous representation. Respect Retry-After on 429 and apply bounded backoff. Subscribe to the registry event stream or signed webhooks when they fit the task.

Authentication and precision

Public registry GETs support cross-origin reads. Account operations use a scoped Fletch bearer key and the x-required-scope in OpenAPI. Keep credentials on your server or local process. A registry:read key does not grant watcher writes or build creation.

Raw token quantities and large block values may be decimal strings. Preserve integer precision and use the token's decimals. A price snapshot is valid only within its own observation window. Ask for provenance before turning a matching ticker into an address in generated code.