Urbit
Urbit is an open-source personal server platform combining Urbit ID — a self-sovereign, Ethereum-anchored identity system (Azimuth) — with Urbit OS, a deterministic operating system built on the Nock virtual machine and the Hoon language. Every user runs their own ship, a self-hosted server whose Eyre HTTP vane exposes the platform's API surface: cookie-authenticated channels (JSON actions in, Server-Sent Events out), read-only scries, and threads, with first-party JavaScript clients published under the @urbit npm scope. The project is notably agent-native: urbit.org publishes a canonical llms.txt, machine-oriented markdown mirrors, public Agent Skills, and a documented MCP path for driving ships from LLM clients. Originally bootstrapped by Tlon and backed by investors including Pantera Capital, the network's identity layer trades as ERC-721 NFTs with a Layer 2 naive rollup (roller.urbit.org) that eliminates gas costs.
Urbit is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Cryptocurrency, Personal Servers, Decentralized Identity, and Peer-to-Peer.
Urbit’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, changelog, and 24 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC) | distribution | 9.6 (thin) | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 2
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
Urbit Ship HTTP API (Eyre)
The HTTP interface of every Urbit ship, served by the Eyre kernel vane. Clients authenticate by POSTing the ship's web login code to /~/login for an urbauth session cookie, then...
Azimuth Layer 2 Roller HTTP RPC-API
The HTTP RPC-API of Azimuth's Layer 2 naive rollup roller, primarily intended for interacting with Bridge. Tlon operates the default public roller at roller.urbit.org, which bat...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Urbit MCP Server
Urbit MCP (%mcp) is a general-purpose Model Context Protocol interface for Urbit, documented in urbit.org's first-party public agent-skill snapshot (/.agents/skills/using-urbit-...
MCP SERVERTerms of Service 1
What its API terms permit and prohibit, quoted from its own page.
Privacy & Data 1
Its role, the data it processes, retention and transfers, quoted from its own privacy page.
Eligibility 1
Who may sign up and where, quoted from its own terms.
AI Preferences 1
Its stance on AI training, inference and agents, quoted from its own pages.
Data License 1
How its data and outputs may be reused, quoted from its own terms.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Urbit API — frequently asked questions
Does Urbit have an API?
Yes. APIs.io lists 2 APIs from Urbit, including Urbit Ship HTTP API (Eyre) and Azimuth Layer 2 Roller HTTP RPC-API.
How do I authenticate with the Urbit API?
Urbit uses bearer-token authentication (cookie-session · 2 schemes). The details are profiled on APIs.io as Urbit Authentication.
Does Urbit have an MCP server?
Yes. APIs.io lists 1 MCP server for Urbit: Urbit MCP (%mcp) is a general-purpose Model Context Protocol interface for Urbit, documented in urbit.org's first-party public agent-skill snapshot (/.agents/skills/using-urbit-apps/references/urbit-m
Is the Urbit API ready for AI agents?
Urbit has a Kin Score of 34.2 out of 100 (thin) and an Agent Readiness score of 12.4 (agent-aware), scored by API Evangelist on 2026-11-13.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.