Developers
The Human API
An ARK is a person in structured form: their knowledge, beliefs, stories and voice, owned by them. The Human API lets your AI or your app ask an ARK, and lets your platform or your AI propose records into it for the owner to review.
Two directions
Read
- Your AI or app
- asks the ARK
- gets an answer or records within its privacy ceiling
Write
- Your platform or your AI
- proposes records
- the owner reviews
- accepted records become part of the ARK
Transports
- REST: one HTTPS endpoint, one POST per action, the action named in the body.
https://www.arkz.ai/api/human - Remote MCP over Streamable HTTP: every tool listed below, for any MCP client that can send a bearer header.
https://www.arkz.ai/mcp - The stdio bridge in the ARKZ repository (mcp/arkz-mcp-server): a local process for clients that only speak stdio. It forwards to the REST endpoint and offers the three live tools only. ask_ark, get_ark_profile, search_ark_topics
What is live and what is Early accessEarly access
Early access: the ARK Record Protocol answers only for ARKs where ARKZ has turned it on. Everywhere else these actions and tools are absent, except get_ark_schema over REST, which answers for every ARK.
Live Live for every ARK with API access: get_ark_profile search_ark_topics ask_ark health
Early access Early access, only where the protocol is on for the ARK: get_ark_schema list_ark_records get_ark_record get_ark_provenance propose_ark_record propose_ark_records get_ark_proposal_status
Machine-readable files
The same definitions these pages render, as files a program can read.