Scott Ai
Scott (by Juno Labs Inc.) is a Y Combinator (F25) planning workspace for engineering teams that build with coding agents. Teams sync recent local agent sessions, push a coding-agent thread into a shareable "planspace", align on design intent through Sync Chat, comments, reviews and approvals, then pull the reviewed context back into execution. Scott ships a first-party CLI/plugin (curl-installed) that wires a Scott skill, rule, and hosted MCP server into Claude Code, Cursor, Codex, OpenCode and Gemini, plus a GitHub App that reviews pull requests against planspace design intent. This profile enriches the provider from its public REST API (api.tryscott.ai, 139 operations), docs, CLI, MCP surface, and security posture.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Scott Ai the way a machine reads it — 36 machine-readable artifacts across 30 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Scott Ai scores 48.1/100 (developing), with a separate agent-readiness read of 81/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Scott Ai
Each block below is one kind of artifact we hold for Scott Ai. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 30
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Scott Ai access API
The access API from Scott Ai — 1 operation(s) for access.
Scott Ai agent-counsel API
The agent-counsel API from Scott Ai — 4 operation(s) for agent-counsel.
Scott Ai agent-counsel-internal API
The agent-counsel-internal API from Scott Ai — 3 operation(s) for agent-counsel-internal.
Scott Ai agent-loop API
The agent-loop API from Scott Ai — 16 operation(s) for agent-loop.
Scott Ai agent-loop-internal API
The agent-loop-internal API from Scott Ai — 3 operation(s) for agent-loop-internal.
Scott Ai artifacts API
The artifacts API from Scott Ai — 1 operation(s) for artifacts.
Scott Ai auth API
The auth API from Scott Ai — 1 operation(s) for auth.
Scott Ai billing API
The billing API from Scott Ai — 5 operation(s) for billing.
Scott Ai cli-version API
The cli-version API from Scott Ai — 1 operation(s) for cli-version.
Scott Ai connected-sources API
The connected-sources API from Scott Ai — 6 operation(s) for connected-sources.
Scott Ai conversations API
The conversations API from Scott Ai — 9 operation(s) for conversations.
Scott Ai documents API
The documents API from Scott Ai — 9 operation(s) for documents.
Scott Ai e2b API
The e2b API from Scott Ai — 2 operation(s) for e2b.
Scott Ai github API
The github API from Scott Ai — 1 operation(s) for github.
Scott Ai github-links API
The github-links API from Scott Ai — 3 operation(s) for github-links.
Scott Ai Health API
The Health API from Scott Ai — 2 operation(s) for health.
Scott Ai integrations API
The integrations API from Scott Ai — 1 operation(s) for integrations.
Scott Ai invites API
The invites API from Scott Ai — 6 operation(s) for invites.
Scott Ai issues API
The issues API from Scott Ai — 1 operation(s) for issues.
Scott Ai notifications API
The notifications API from Scott Ai — 5 operation(s) for notifications.
Scott Ai One Shot API API
The One Shot API API from Scott Ai — 1 operation(s) for one shot api.
Scott Ai orgs API
The orgs API from Scott Ai — 1 operation(s) for orgs.
Scott Ai probes API
The probes API from Scott Ai — 3 operation(s) for probes.
Scott Ai reviews API
The reviews API from Scott Ai — 9 operation(s) for reviews.
Scott Ai snapshots API
The snapshots API from Scott Ai — 7 operation(s) for snapshots.
Scott Ai sync-chat API
The sync-chat API from Scott Ai — 8 operation(s) for sync-chat.
Scott Ai users API
The users API from Scott Ai — 8 operation(s) for users.
Scott Ai waitlist API
The waitlist API from Scott Ai — 1 operation(s) for waitlist.
Scott Ai walkthroughs API
The walkthroughs API from Scott Ai — 3 operation(s) for walkthroughs.
Scott Ai .well Known API
The .well Known API from Scott Ai — 1 operation(s) for .well known.
Scroll within the panel for all 30 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
scott-ai-mcp.yml
MCP SERVERSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Scott Ai — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/scott-ai · machine-readable index on apis.io