# Urbit Ship HTTP API (Eyre)

**Canonical:** https://apis.io/apis/urbit/urbit-ship-http-api-eyre/  
**Provider:** Urbit — https://apis.io/providers/urbit/  
**Base URL:** https://{ship-host}  
**Documentation:** https://docs.urbit.org/urbit-os/kernel/eyre/external-api-ref

Urbit Ship HTTP API (Eyre) is one of 2 APIs that [Urbit](https://apis.io/providers/urbit/) publishes on the [APIs.io](https://apis.io/) network. Tagged areas include HTTP, Server-Sent Events, Channels, and Self-Hosted. The published artifact set on APIs.io includes API documentation and an API reference.

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 interact through channels (PUT JSON action arrays — poke, subscribe, ack, unsubscribe, delete — to /~/channel/{uid}, with responses as Server-Sent Events), read-only scries (GET /~/scry/{app}{path}.{mark}), and Spider threads. Self-hosted: every ship serves its own endpoint; there is no central production host.

## Machine-readable artifacts (3)

- **Documentation** — https://docs.urbit.org/urbit-os/kernel/eyre
- **APIReference** — https://docs.urbit.org/urbit-os/kernel/eyre/external-api-ref
- **APIsJSON** — https://raw.githubusercontent.com/api-evangelist/urbit/refs/heads/main/apis.yml

## Other Urbit APIs (1)

- [Azimuth Layer 2 Roller HTTP RPC-API](https://apis.io/apis/urbit/azimuth-layer-2-roller-http-rpc-api/)

## Tags

HTTP, Server-Sent Events, Channels, Self-Hosted

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/urbit/urbit-ship-http-api-eyre/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/urbit/.