Ask the agent field a precise question.

How do you start a public search?

You can search the public graph without a bearer token. Send a phrase and page size to the endpoint below. A project key gives the request its own usage limit. It does not unlock private records, unpublished research, licensed fields, or another customer’s material.

curl 'https://api.agentmode.ai/v1/search?q=model%20context%20protocol&page_size=10' \
  -H 'X-AgentMode-Project-Key: amp_example_not_a_real_key'

What does authentication allow?

Licensed fields require three things: a verified identity, the graph:read:licensed scope, and an active Graph API purchase. You need all three. Version one never returns unpublished records, and an error will not tell you whether a private record exists. No shortcut joins those checks.

Which endpoints are available?

The first version gives each job its own read endpoint. Search finds public records. Node and edge routes inspect one object. Claim and source routes show what supports it. Release routes give you checksums. Every response still follows the field and access rules for that record.

• GET /v1/search finds published graph records.
• GET /v1/nodes/{nodeId} reads one record through an allowed field projection.
• GET /v1/nodes/{nodeId}/neighbors reads at most two precomputed hops.
• GET /v1/edges/{edgeId}, /claims/{claimId} and /sources/{sourceId} show the evidence behind a relationship.
• GET /v1/graph/releases/{releaseId} returns checksums and export metadata.

Which limits can clients rely on?

A page starts with 25 records and never exceeds 100. Search stops at 50 results. Neighbor reads stop at two prepared hops. Cursors are signed and should be treated as opaque. If the graph changes while you are paging, start again so you do not mix two releases.

How do errors and caching work?

Every response includes a correlation ID you can use for support. Errors never include credentials, stack traces, or clues about private records. Stable reads return an ETag. Send it in If-None-Match; if nothing changed, the API can answer with a bodyless 304 response.

How are API versions changed?

A breaking change gets a new major number in the URL. A generally available major gets at least 12 months of notice, a migration guide, and dated deprecation headers. Security or legal exceptions must be documented and approved; they cannot quietly change an existing response or remove access.

The production endpoint is not open yet. The example key on this page is fake.