How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Amika website screenshot

Amika

Amika is a Y Combinator-backed infrastructure company for running AI coding agents in isolated cloud sandboxes. Teams spawn agents from Slack, Linear, GitHub, a CLI, a TypeScript SDK, or the hosted HTTP API to understand a codebase, run in a root-access VM, execute programmable checks (tests, linters, type checkers), and open validated pull requests autonomously. The platform exposes a REST API (v0beta1) for managing repositories, sandboxes, snapshots, agent sessions, secrets, services, storage, and Slack integration, with API-key and OAuth device-flow authentication. Core primitives are shipped open source under the gofixpoint GitHub organization, including the amika CLI, the amikalog session-capture tool, and the @amika/sdk TypeScript client.

agent aware

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.

Kin Score

API Evangelist profiles Amika the way a machine reads it — 27 machine-readable artifacts across 1 API, 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 — Amika scores 51.3/100 (developing), with a separate agent-readiness read of 19/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-10 · rubric v0.20.0
Amika Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Amika's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amika/"
   title="Amika on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/amika.svg"
       alt="Amika Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Amika

Each block below is one kind of artifact we hold for Amika. 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 12

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.

Amika API keys API

The API keys API from Amika — 2 operation(s) for api keys.

Amika Docker registries API

The Docker registries API from Amika — 2 operation(s) for docker registries.

Amika Downloads API

The Downloads API from Amika — 1 operation(s) for downloads.

Amika Git user settings API

The Git user settings API from Amika — 1 operation(s) for git user settings.

Amika Integrations API

The Integrations API from Amika — 2 operation(s) for integrations.

Amika Repositories API

The Repositories API from Amika — 5 operation(s) for repositories.

Amika Sandboxes API

The Sandboxes API from Amika — 16 operation(s) for sandboxes.

Amika SandboxSnapshots API

The SandboxSnapshots API from Amika — 3 operation(s) for sandboxsnapshots.

Amika Secrets API

The Secrets API from Amika — 11 operation(s) for secrets.

Amika Services API

The Services API from Amika — 2 operation(s) for services.

Amika Slack API

The Slack API from Amika — 2 operation(s) for slack.

Amika Uploads API

The Uploads API from Amika — 2 operation(s) for uploads.

Scroll within the panel for all 12 ·

Open Collections 13

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 13 ·

Security Posture 2

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.

Amika Authentication

http/apiKey/oauth2 · 4 schemes

SECURITY

Amika Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Amika — 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.

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Access & Security 2

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/amika · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Amika, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.