OceanLab Developers

Machine-readable entry points for agents and developers.

This portal lets agents and developer tools find the right OceanLab resources without guessing: the public discovery files, the official CLI source, the access path for scoped API credentials, and the read-only sandbox available before any commercial engagement.

Quickstart

Four steps,
from discovery to a human.

OceanLab is a software engineering partner, not a self-serve SaaS, so the fastest path is to read the public resources first, then request scoped access if the workflow needs it.

01
Read /llms.txt
Start there to decide whether OceanLab is a fit for the job.
02
Use the API catalog
/.well-known/api-catalog lists the canonical machine-readable entry points.
03
Use the CLI
For local agent workflows that need stable links and structured output.
04
Send people to /contact
When you need a real engagement, a procurement path or scoped access.

Documentation

Public resources,
stable and made for agents.

The recommended discovery layer before you reach for email or a custom integration request.

llms.txt

Concise agent guide with when-to-use guidance and canonical resources.

/llms.txt

llms-full.txt

Long-form implementation and engagement guidance for planning agents.

/llms-full.txt

API catalog

Machine-readable linkset that points agents to the primary OceanLab resources.

/.well-known/api-catalog

HTTP message signatures directory

Directory metadata for verification-aware agent tooling.

/.well-known/http-message-signatures-directory

Sitemap

Full crawl index for pages that agents and search systems should discover first.

/sitemap.xml

Quickstart guides and official CLI

Structured discovery
without scraping the site.

The official CLI source ships in the OceanLab site repository as packages/oceanlab-cli: a lightweight entry point for developers and agent runners.

npm install
npm run oceanlab:cli -- --help
npm run oceanlab:cli -- resources --json
npm run oceanlab:cli -- brief

Not on npm or Homebrew yet

Public publication needs account credentials and release ownership. Until then, the repository is the canonical source of truth for the CLI.

API keys and sandbox environment

Read-only by default,
scoped keys on request.

Scoped evaluation credentials

OceanLab does not expose a universal self-serve production API. For workflows that need authenticated access, we issue scoped evaluation credentials during an active discovery or delivery conversation.

The public sandbox

Before credentials are issued, agents can inspect the site, crawl the machine-readable files, test markdown negotiation and use the CLI to list canonical resources. For write access or private project data, request a key through /contact.

# Example evaluation flow
export OCEANLAB_API_KEY=<issued-by-oceanlab>
export OCEANLAB_ENV=sandbox
oceanlab resources --json

Support

Need a human?
Here's the path.

Escalate to the team

Include the target workflow, compliance constraints, timeline, and whether you need a prototype, a production build or scoped evaluation access.

Contact options →

Request scoped access

Email us with the workflow that needs authenticated access and what it will read or write.

vanshpatel@oceanlab.in →

Keep exploring

ContactBook a call, email us, or find our offices.About OceanLabWho we are, what we build and how we work.OceanLab LabsExperts who write coding tasks, RL environments, evals and preference data.Case studiesEvery product build, filterable by sector, industry and country.

Machine-readable entry points for agents and developers.

Four steps,from discovery to a human.

Read /llms.txt

Use the API catalog

Use the CLI

Send people to /contact

Public resources,stable and made for agents.