Developer & Agent Resources

Every machine-readable document Ivy publishes, in one place. No key, no signup, no rate-limit negotiation — every endpoint below is a public GET.

Ivy is built to be consumed by software as readily as by people. The site serves an OpenAPI 3.1 description of its public surface, llms.txt summaries for answer engines, discovery documents under /.well-known/, and a text/markdown rendition of every marketing page via Accept-header negotiation. Everything on this page is stable, versioned, and safe to automate against.

API specifications

Machine-readable descriptions of the public API. Both documents are generated from one source, so they can never drift apart.

OpenAPI 3.1 specification (JSON)

/openapi.json

Complete description of every public operation, with typed response schemas and RFC 9457 problem details.

OpenAPI 3.1 specification (YAML)

/openapi.yaml

The same specification serialized as YAML for tooling that prefers it.

Public agent API

Four unauthenticated JSON endpoints describing what Ivy is, when an agent should reach for it, and where to download it.

Agent capabilities

/api/v1/agent/capabilities

Supported coding agents and language models, with the feature matrix for each.

Agent instructions

/api/v1/agent/instructions

When to use Tendril, when not to, how to call it, and the onboarding path.

Company and product context

/api/v1/agent/context

Organisation details, product catalogue, pricing tiers, and the full endpoint map.

Release downloads

/api/v1/agent/downloads

The current Tendril release with installer URLs for every supported platform.

Answer-engine resources

Plain-text summaries written for large language models, following the llms.txt convention.

llms.txt summary

/llms.txt

Concise overview of Ivy, Tendril, developer resources, and how agents should call them.

llms-full.txt extended summary

/llms-full.txt

Expanded edition covering every marketing page, pricing tier, and published article.

agent-instructions.txt

/agent-instructions.txt

Operating instructions for autonomous agents evaluating or installing Tendril.

Discovery documents

Well-known URIs that let a client configure itself without being told where anything lives.

Model Context Protocol manifest

/.well-known/mcp.json

MCP server descriptor for agents that speak the Model Context Protocol.

Universal Commerce Protocol manifest

/.well-known/ucp/manifest.json

Provider identity, service category, and pricing, declared for commerce agents.

security.txt

/.well-known/security.txt

Where to report a security vulnerability, per RFC 9116.

Markdown content negotiation

Send Accept: text/markdown to any marketing page and you get clean markdown instead of HTML — no scraping, no DOM parsing. This follows the acceptmarkdown.com convention.

curl -H 'Accept: text/markdown' https://ivy.app/product

Rate limits

Public endpoints advertise a request budget with the RateLimit headers from the IETF draft standard, so a client can discover the ceiling instead of finding it by being cut off. Documents are served from cache and revalidate hourly, so a client that honours Cache-Control cannot exhaust the budget. If a budget is ever exceeded the response is 429 with a Retry-After header and an RFC 9457 problem document.

RateLimit-Limit — requests permitted in the current windowRateLimit-Remaining — requests still availableRateLimit-Reset — seconds until the window resetsRateLimit-Policy — the policy expressed as quota and window

Versioning and deprecation

Agent endpoints are versioned in the path (/api/v1/). Breaking changes ship under a new version rather than mutating an existing one. When an operation is retired it is first marked deprecated in the OpenAPI document and serves Deprecation and Sunset headers for at least 180 days before removal, per RFC 9745 and RFC 8594.

Build with Ivy

Tendril is source-available and the orchestration layer runs on your own machine.

Ivy Tendril on GitHub Tendril documentation