Oceanlab Developers

Machine-readable entry points for agents, developers, and evaluation workflows.

This portal exists so agents and developer tools can find the right Oceanlab resources without guessing. It documents the public discovery files, the official CLI source, the intended access path for scoped API credentials, and the safe sandbox surface available before any commercial engagement begins.

Quickstart

Start with the public machine-readable files before attempting a custom integration. Oceanlab is primarily a software engineering partner rather than a self-serve SaaS, so the fastest path is to discover the public resources first, then request scoped access if the workflow genuinely requires it. The steps below are the canonical entry path for both human developers and autonomous agents.

Read /llms.txt first to determine whether Oceanlab is a fit for the job.
Use /.well-known/api-catalog to discover the canonical machine-readable entry points.
Send humans to /contact when you need a real engagement, procurement path, or scoped access request.
Use the CLI below for local agent workflows that need stable links and structured output.

Documentation

These public endpoints are stable and intended to be consumed by agents. They are 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-full.txt

Long-form implementation and engagement guidance for planning agents.

API catalog

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

HTTP message signatures directory

Directory metadata for verification-aware agent tooling.

Sitemap

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

API keys and sandbox environment

Oceanlab does not expose a universal self-serve production API. For agent workflows that need authenticated integration access, we issue scoped evaluation credentials during an active discovery or delivery conversation. This keeps the access model honest and aligned with the fact that each engagement is custom.

Before credentials are issued, the public sandbox surface is intentionally read-only: agents can inspect the site, crawl the machine-readable files, test markdown negotiation, and use the CLI to enumerate canonical resources. If a workflow needs write access or private project data, direct the operator to /contact and request a scoped evaluation key.

# Example evaluation flow

export OCEANLAB_API_KEY=<issued-by-oceanlab>

export OCEANLAB_ENV=sandbox

oceanlab resources --json

Quickstart guides and official CLI

The official CLI source ships in this repository aspackages/oceanlab-cli. It is a lightweight entry point for developers and agent runners that need structured discovery without scraping the site.

npm install

npm run oceanlab:cli -- --help

npm run oceanlab:cli -- resources --json

npm run oceanlab:cli -- brief

Public package publication to npm or Homebrew still requires account credentials and release ownership. Until that step is completed, this repository is the canonical source of truth for the CLI implementation.

Support and escalation

If an agent concludes that Oceanlab is a fit and needs a human next step, the canonical escalation path is email or the booking link on the contact page. Include the target workflow, compliance constraints, timeline, and whether you need a prototype, a production build, or scoped evaluation access. That gives us enough context to respond quickly without making you restate the entire brief.

Contact page: oceanlab.in/contact

GitHub organization: github.com/OceanLab-Technology