Evrim
Evrim is the upstream signal layer for U.S. financial institutions, the defense industrial base, and federal agencies. The Evrim REST API ("Data when and how you want it.", v0.5.18) builds structured intelligence profiles from reusable templates and fields, captures point-in-time snapshots, and extracts values and relationships from source content. Every operation authenticates with a Knox-issued API token sent as an HTTP Bearer credential, and an official Stainless-generated Python SDK is published on PyPI.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Evrim the way a machine reads it — 21 machine-readable artifacts across 18 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 — Evrim scores 32.6/100 (thin), with a separate agent-readiness read of 43/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Evrim
Each block below is one kind of artifact we hold for Evrim. 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 18
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.
Evrim answers API
The answers API from Evrim — 2 operation(s) for answers.
Evrim blank API
The blank API from Evrim — 2 operation(s) for blank.
Evrim bulk API
The bulk API from Evrim — 3 operation(s) for bulk.
Evrim collections API
The collections API from Evrim — 2 operation(s) for collections.
Evrim compose API
The compose API from Evrim — 1 operation(s) for compose.
Evrim costs API
The costs API from Evrim — 8 operation(s) for costs.
Evrim created-fields API
The created-fields API from Evrim — 3 operation(s) for created-fields.
Evrim extract API
The extract API from Evrim — 8 operation(s) for extract.
Evrim fields API
The fields API from Evrim — 3 operation(s) for fields.
Evrim health API
The health API from Evrim — 2 operation(s) for health.
Evrim prod API
The prod API from Evrim — 1 operation(s) for prod.
Evrim profiles API
The profiles API from Evrim — 10 operation(s) for profiles.
Evrim prompt-templates API
The prompt-templates API from Evrim — 2 operation(s) for prompt-templates.
Evrim questions API
The questions API from Evrim — 1 operation(s) for questions.
Evrim snapshots API
The snapshots API from Evrim — 2 operation(s) for snapshots.
Evrim tags API
The tags API from Evrim — 4 operation(s) for tags.
Evrim templates API
The templates API from Evrim — 3 operation(s) for templates.
Evrim transform API
The transform API from Evrim — 1 operation(s) for transform.
Scroll within the panel for all 18 ·
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.
evrim-mcp.yml
MCP SERVERSecurity 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.
Resources
Every other property we hold for Evrim — 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 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
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/evrim · machine-readable index on apis.io