Developer Infrastructure · Dino

Agent-led onboarding

A coding agent onboards an organisation's whole API estate into Dino over MCP, and people make every consequential decision.

Founder · Architect · Full-Stack Engineer

How it works

The agent registers the API, its environments and targets, describes how Dino should sign in, and proposes where scans run. Whenever a person must decide, Dino raises a Human Action Request: entering a secret, choosing where scans run, authorising the connection. The agent cannot approve these itself. Requests are durable, so onboarding pauses and resumes cleanly, and access can be withdrawn per member and per client.

The flow runs end to end in production, from a brand-new organisation to discovery.

System

Built into the agent: MCP, CLI, skills and assistant

Dino puts API knowledge, context retrieval, findings and quality checks directly inside coding agents through MCP, with a developer CLI, agent skills and a natural-language API assistant.

MCPCLIAI agents

System

Secret custody

The credentials Dino uses to test an API never enter chat, logs or Dino's own database.

SecuritySecrets

System

API discovery

Dino finds every operation an API exposes, REST and GraphQL, with its schemas, authentication requirements, dependencies and relationships, and keeps that inventory current.

DiscoveryOpenAPIGraphQL

Agent-led onboarding

How it works

Related systems

Built into the agent: MCP, CLI, skills and assistant

Secret custody

API discovery

How it works