Quickstart: use the API

One request returns a token's recorded trust verdict, metadata and observation time.

Last verified against production: 2026-09-08. See current limits and availability.

Create a scoped key

Sign in, open Dashboard → Settings → API keys and name a key. Choose Read the registry (registry:read) for this example, then Create key.
Copy the key when it is shown. Keep it in your local environment as FLETCH_API_KEY. This is a Fletch API credential; model provider keys belong in the separate model connection form.
Run the request below. Inspect trust, source, address, symbol and readAt. Use impersonates when the verdict is lookalike. Use the complete address as the identity.

curl --fail-with-body --silent --show-error \
  -H "Authorization: Bearer $FLETCH_API_KEY" \
  https://fletch.now/api/v1/tokens/0x6bac06600d220ac5ac281ad1f504d2cf0f90f6e6

Create a key in Settings

Read the response

The response is JSON. trust is verified, listed, lookalike, community or unknown. readAt is the observation time, source names the registry or discovered record, and null means a fact is unavailable. market may be null even when the token is known.

Public registry reads also work without the Authorization header. Account operations require the scope named by their OpenAPI entry. A 401 indicates missing or invalid authentication, a 403 a missing scope, and a 429 a rate limit. Honor Retry-After before retrying.

curl --fail-with-body --silent --show-error https://fletch.now/api/v1/status