Records
Current world context
Read entities, places, events, domain records, and the time each record describes.
Machine access, by approval
Give agents a grounded view of the world.
AgentLayer lets approved software read Planetary Model records across the Earth domains relevant to its work. A response can include the record, its sources, what is missing, and what the caller may use.
Sources
Evidence that travels
Keep source references, history, uncertainty, and contradictions attached to the answer.
Limits
Clear boundaries
Return a denial, redaction, or blocker when the caller lacks access or the record is not strong enough.
Delivery
One contract family
REST, MCP, A2A, and SDK shapes are verified in the repository. Connection details are supplied through an approved handoff.
Why agents need it
A useful agent response names the record, its date, the supporting sources and what the caller may do with it.
REST
versioned contract shapes
MCP + A2A
the same read rules
Evidence
sources stay attached
Access
scope, redaction, audit
What agents can do
Ask about the world. Keep the sources with the answer.
Find a missing fact
research or operations agent
Check the approved record and customer context for stale assumptions, missing evidence, or a contradiction that needs review.
Understand what changed
monitoring agent
Ask about an entity, place, market, or domain and return the recorded change with its time and source trail.
Inspect maritime activity
maritime agent
Bring together relevant context about vessels, ports, routes, trade, weather, infrastructure, ownership, and compliance without reducing maritime to one risk category.
Connect signals across domains
industry or supply chain agent
Follow a change across companies, infrastructure, commodities, policy, logistics, and other relevant parts of the Earth system.
Brief a human owner
customer agent
Return a concise answer with the supporting records and any limits, instead of filling gaps with generated certainty.
Watch for a real change
workflow agent
Read approved updates, check the evidence, and leave the decision to the customer workflow or human reviewer.
AgentLayer Protocol
One set of rules across REST, MCP, A2A, and SDKs.
Each interface reads from the Planetary Model under the same access rules. Accepted state is read only through AgentLayer. The contract is available for inspection.
REST and OpenAPI
Versioned JSON shapes for records, evidence, and updates.
MCP and A2A
Agent tools and agent calls over the same read rules.
Typed SDKs
TypeScript and Python helpers exist in the repository. Registry packages are not published.
Access controls
Scopes, redaction, and audit details stay in the response.
Current availability
The contracts work locally. The hosted service is not generally available.
The repository proves how AgentLayer authenticates callers, checks access, returns records, and refuses unsupported answers. It does not yet prove a public production runtime at api.crowdalpha.ai.
Proven in the repository
- Local tests cover bearer authentication, scope checks, entitlement checks, tenant isolation, and successful read envelopes.
- Contract tests cover records, evidence references, blockers, redaction, and typed decision inputs.
- TypeScript and Python helpers are exercised against a local FastAPI process. They are repository code, not public registry releases.
In progress
- External proof for the hosted API, database scale, recurring sources, monitoring, and production limits.
- Public SDK packages, self service keys, and public install commands.
- Customer uploads and other write paths. Current public contracts are read first and do not let agents write into accepted state.
- Wider access across Earth domains as source rights, evidence, and customer scope are approved.
Repository runbooks record the local checks behind these claims. An approved deployment handoff is still required for hosted use.
AgentLayer lets software read the Planetary Model without losing the source trail.
An approved handoff provides the connection details and scope for each deployment.