API documentation

API docs that stay accurate because they sit next to the work.

Osco keeps your API reference in the same workspace as the tasks that change it. Developers can read, try requests against real environments and share a read-only link with partners.

Get started free Talk to sales

The problem

What gets in the way today

The API reference lives in a separate tool and drifts from what the code does.
Developers copy requests into a separate client just to try an endpoint.
Sharing docs with a partner means giving them access to everything or exporting a PDF.

How Osco helps

Context that travels with the work

Every endpoint documented the same way

Method, path, parameters, headers, body, auth and example responses, organised in folders.

Try it where you read it

Send requests from the explorer using environments such as staging and production.

Linked to the work

Attach endpoints to tasks and features, so the person changing an endpoint sees its docs at the right moment.

Share safely

Create a workspace-only or public read-only link to a single endpoint, with an optional expiry, and revoke it any time.

How it works

From setup to everyday use

1
Document
Add endpoints with their parameters, auth and example responses.
2
Configure
Set up environments with base URLs and variables for each stage.
3
Connect
Link endpoints to the tasks and features that change them.
4
Share
Send partners a read-only link instead of a workspace invite.

Frequently asked questions

Can partners read our API docs without an account?

Yes, if you create a public share link for an endpoint. Workspace-only links require sign-in as a member.

Can coding agents read the API reference?

Yes. Over the Osco MCP server, an agent can read endpoints with the same permissions as the person who connected it.

Who can create public links?

Only roles with the public sharing permission. Admins can see and revoke every active link in settings.

More use cases

Developer onboardingGet new engineers shipping in days, not weeks, with docs and tasks that explain themselves.Architecture & decisionsKeep architecture docs, diagrams and decision records connected to the features they explain.Coding agents & MCPGive Claude Code, Cursor and other MCP agents the same context your engineers use.Context-rich tasksTasks that carry their why, acceptance criteria, dependencies and links, so work starts without a meeting.Partner & client sharingShare a single doc or endpoint with people outside your workspace, read-only and revocable.

Give every task the context to finish it.

Start free with your team. Bring your Markdown, connect your coding agents and invite people when you are ready.