Free · no account · facts at a stated time

The record

What public AI agents, MCP servers and online shops published, with the date GAIP read it, kept in hash chains anchored each day in public logs GAIP does not run. Every answer drawn from it is signed. Facts at a stated time, never an assessment of any party.

Why a dated record

What it is. A dated record is a note of what a party published, made when it was published, with the time attached. GAIP reads what AI agents, MCP servers and online shops publish for machines (agent cards, tool lists, robots.txt and AI-permission files, signing keys, declared prices) and writes down what it saw and when. Each entry carries the hash of the entry before it, so a later change to an earlier entry would show.

Why it cannot be back-filled. Every day GAIP signs the newest hash of each chain through Sigstore's public transparency log (Rekor) and timestamps it with OpenTimestamps, whose proof is then tied to a Bitcoin block. GAIP runs neither. Once a day's head is in those logs, an entry cannot be added before it, removed or changed without the published heads no longer matching. Anyone can start reading agents today; nobody can now read what an agent published on the day GAIP's record began. The value is in the dates, and a date cannot be added later.

Why a party that vouches for nobody. GAIP does not approve or recommend any agent, shop or business, does not compare one with another, and nothing in the record can be bought: no party pays to appear in it, to change it or to be left out. It says what was published and when, and what its answer does not say. That is why both sides of a dispute can cite the same receipt: a buyer's agent and a seller's agent read one record that neither of them wrote and that takes neither side. A record that vouched for someone would be useful to that someone; a record that vouches for nobody can be cited by everyone who needs to agree on what happened.

What GAIP keeps that others do not. A registry lists what an agent says about itself now; GAIP keeps what it said on each date since GAIP began reading it, including what it later changed or withdrew. A bot-authentication scheme (signed requests, lists of known bots) shows which key sent a request now; GAIP records which keys a host published in each week, so a key can be checked against the date it was used. An identity or KYB vendor vouches for who a business is, usually paid by that business; GAIP vouches for nobody, records what each side published and when, and signs every answer with a key anyone can check offline (the receipt verifier). These do different jobs: GAIP reads registries, keys and company registers as sources and does not replace them.

What GAIP records, how it is checked and how long it is kept: the data record and the method. Something wrong? Corrections.

Every question the record answers

One card per line of GAIP's map, with its MCP tools (on /mcp/all) and HTTP routes. Free, no account or key. Every answer says what it does not say.

The record, by date

Seven free reads answer one subject on one date from what GAIP has recorded since 28 Sep 2026, with the week each fact was recorded. Every answer carries answer_sha256 and GAIP's Ed25519 signature (keys at /.well-known/gaip-receipt-keys.json). The same seven are MCP tools on /mcp/all. Facts GAIP recorded, never an assessment of the party.

Tenure

Since when GAIP has recorded an endpoint, how many days it has a record and answered, its registry version and endpoint changes and the names it declared. With only your continuity handle (X-GAIP-Continuity), how long you have been coming back to GAIP. GAIP's observation, never a creation date, and not a measure of trust: a long record is not a reason to rely on an agent, and a short one is not a reason to avoid it.

/v1/free/record/tenure?url=https://huggingface.co/mcp

Names

Since when a registry name has been on record, in which registries, and the earlier names that look like it (the same last segment, one or two edits apart, or look-alike characters). Not yet published? Ask about the name you plan to use and see what already looks like it. The publisher can reply: POST /v1/free/record/names/reply, or object: POST /v1/free/record/names/objection. Dated facts; the decision stays with you.

/v1/free/record/names?name=io.github.upstash/context7

Keys

The keys a host published in the week of a date (JWKS, Web Bot Auth directory, A2A card signature key ids, OAuth signing keys, each with its public JWK members; ERC-8004 registration bindings by endpoint name, DID method and chain only, never a value or a digest of it), and with kid= or thumbprint= the weeks it was published, with any recorded week in between that did not list it. GAIP Watch flags a key change as key_changed.

/v1/free/record/keys?host=mcp.notion.com

Permissions

What a site's robots.txt said for an AI agent on a date (ALLOWED, DISALLOWED, NOT_NAMED or NO_RULE) with the rule quoted, and every robots.txt, llms.txt, ai.txt and TDMRep version with the weeks it was in force. What the file said, not whether a use was lawful. Also the site's AI-preference declarations (IETF Content-Usage, RSL licence links) with the weeks each was in force.

/v1/free/record/permissions?host=huggingface.co&agent=GPTBot

Prices

The prices a service declared in the week of a date (x402, on its MCP tools, in its ai-catalog.json), the weekly series and the week of the last change. The pay-to address is never kept.

/v1/free/record/prices?host=huggingface.co

Ingredients

What the agent's own documents (card, initialize answer, tool descriptions, llms.txt) said on a date: the provider, version and model they name (with the excerpt), the operator, and whether they contain a statement that the agent is an AI (PRESENT, NOT_FOUND or NOT_READ), with the dates the declaration changed. What the agent's published documents said on the stated date; a declared model is declared, not verified; whether any disclosure duty applied is not assessed.

/v1/free/record/ingredients?url=https://huggingface.co/mcp

Residence

Where the endpoint answered from on a date, from the connection GAIP already made: the network (ASN) and its registered country, the certificate issuer and subject organisations, any region the provider declares, and the dates its hosting changed. The address itself is never kept. Where the endpoint answered from, as GAIP observed it; not where its data is processed, and not a statement about any transfer.

/v1/free/record/residence?url=https://huggingface.co/mcp

Whether every collector behind these is running now: collection status. The whole record in one signed request: /.well-known/gaip-record.json. Open data: /data.

Put the date in your README

If GAIP records an agent card or MCP endpoint on your host, this image shows the date GAIP's record of your host begins, read from the record each time it is drawn (cached for an hour). Any other host gets a grey "not on GAIP's record" image. It is a dated fact, not an assessment of your host or your agents.

[![On GAIP's record](https://www.gaipagents.com/v1/free/badge/record-since.svg?host=<your host>)](https://www.gaipagents.com/v1/free/host-timeline?host=<your host>)

For example, huggingface.co:

What the record can answer

• Does this agent, server or API work, and has it changed? Check and GAIP Watch: A one-line verdict, the fixes, dated history where GAIP observes it, and a receipt; GAIP Watch follows it for changes. Any agent · gaip_check, gaip_watch
• A call failed; what went wrong? Diagnose: The cause, when to retry and the exact fix, from the error text and HTTP status you paste. Any agent · gaip_diagnose
• Was this delivery or quotation what was promised? Witness: Witness tests a service's response against the terms you registered, or cited pages against the quoted text, with a receipt for each. A company's agent · gaip_verify, witness_register_terms, witness_delivery
• What did a site allow, publish, key or charge on a date? The record by date: Its robots.txt permissions for a named AI agent, its signing keys and its x402 prices in the week of that date; since when GAIP has recorded an endpoint or a registry name, and which earlier names look like it. A company's agent · gaip_record_permissions, gaip_record_prices, gaip_record_keys, gaip_record_names, gaip_record_tenure, gaip_record_extract, gaip_check_permission
• Has anyone withdrawn it or warned about it? Notices: Registry status flips, an operator's own withdrawal, package advisories, each with the issuer named and the operator's reply. A company's agent · gaip_notices, gaip_dependency_check
• May I contact this person's agent? Preferences: Before an agent approaches a person it checks their published rules and keeps a receipt. A company's agent · gaip_check_preferences
• Was this business deal kept? Deals: Both trading agents name GAIP as witness; either party asks for the signed finding on the agreed rule, over GAIP's own delivery records. Evidence, never a sum of money. A company's agent · witness_accept_terms, witness_finding
• Who is calling me, and should I pick up? The caller screen: When an agent approaches yours, the caller screen shows how long it has been on record and whether it checked first. Facts, never a score; GAIP cannot block a call. A person's agent · gaip_screen_caller
• Does the shop's own page show the price and stock an AI quoted? Second Look: Second Look reads the shop's own page now and records what it showed beside what the claim said, with a signed, dated receipt. No affiliate links. A person's agent · second_look_check
• Was this agent authorised to act for them? Mandates: Whether a person's published mandate for an agent was in force, withdrawn or expired as GAIP indexed it, with a receipt. A person's agent · gaip_check_mandate
• Who signed off on this decision, and when? Sign-offs: A role records its decision on an agent's proposal, chained and signed; GAIP never takes the decision. A person's agent · witness_signoff
• What is this agent made of, and where does it live? Ingredients and Residence: As recorded on a date: what its documents say it runs on, and where it answered from (network and country, never the address). Any agent · gaip_record_ingredients, gaip_record_residence
• What did my agents do this month? Statements: A signed monthly record of what GAIP recorded for the agents bound to your continuity handle, with every line's receipt; served only to that handle. Any agent · gaip_statement

One question per line of GAIP's map (gaip.map.v1), with its tools; each line's route and what it does not say are in the cards above, and the record by date in bulk is on the open data page. For agents, the whole record in one signed request: /.well-known/gaip-record.json. Whether collection is running now · Open data.