com.apievangelist/api-evangelist

Measure how much of an API description your governance actually inspects — coverage by section, each rule's reach, and the rules that match nothing. Like test coverage, one altitude up.

Score an API's maturity 0-100 with a letter grade across design, governance coverage, documentation, and (from an apis.json) discoverability, agent-readiness, and operations. Pass your own `ruleset` — a score against rules you never adopted means little.

Apply an OpenAPI Overlay to a document and report what each action matched. Use it for deprecation and migration choreography without forking the contract.

Score a repository's Spectral CI setup against an 8-point maturity rubric and return a prioritized punch-list. Pass a public `repo` ("owner/name") or `files`.

PRO — Adopt a ruleset on a legacy API without a wall of red: snapshot today's violations as a baseline, then pass that baseline back to fail only on NEW violations (with fixed counts, a warning budget and burndown).

Issue a tamper-evident governance certificate attesting an API passed a named ruleset at a profile threshold. A SHA-256 fingerprint lets anyone re-verify it.

Inventory the PII, secret, and sensitive fields an OpenAPI exposes, across parameters and request/response schemas. Run this before exposing an API to agents.

Generate runnable curl, JavaScript, and Python samples for every operation, with path params filled in and a realistic body.

PRO — a company's investment dimensions, each read AGAINST the measured cohort: the cohort median, mean and max, this company's rank and percentile, and an index where 1.0 is exactly typical. A raw dimension score is unreadable on its own; these are the columns that make it mean something.

A company's weakest investment dimensions — where it is thin. Pro.

PRO — the companies most comparable to this one (same sub-sector where the data supports it, same industry otherwise), each with signal totals and top dimensions. The response says which basis it used.

PRO — the company's adopted stack entity by entity (services, tools, standards), each with how many companies across the cohort carry it and its radar ring.

PRO — what this company's peers run that it does not, ranked by how many peers carry it. The opening list for a vendor selling into the account.

Report every deprecated operation and whether it actually announces a sunset. The ones that go quiet are the ones that break consumers.

Look up one rule by id — description, severity, given/then, reference — and its remediation prompt: what to change when it fires. Suggests close matches for an unknown id.

Identify a document: OpenAPI (Swagger 2.0 vs 3.x), AsyncAPI, Arazzo, JSON Schema, APIs.json, MCP, an agent SKILL.md, an Overlay or a ruleset — and how many catalog rules and which named profiles apply.

Compare two OpenAPI versions and classify every change as breaking, non-breaking, or an addition — at path, operation, parameter, request-body, and response granularity.

Generate human-readable Markdown documentation for a ruleset — each rule's severity, what it checks, its message and how to fix it. Pass `ruleset`, or `profile` for a curated one (owasp, problem-details, fhir, api-authorization).

PRO — THE INVERSION. Every other insights tool runs company -> stack; this one runs stack -> companies: which companies show demand for a given service, tool or standard, broken down by industry. This is the prospecting query — "who should I be selling this to" — and it exists in no report, bundle or page. Returns BOTH the authoritative company count and the companies it can actually name, with the basis difference explained.

Explain why a rule did or did not fire on a document: whether its formats matched, what its `given` matched, what `then` checked, and the verdict. Works for your own rules, the catalog, and the built-ins.

Turn a governance ruleset into agent-native guidance — an AGENTS.md block, a system-prompt set, a per-rule remediation pack, and a digest — so agents follow the rules while authoring, not after linting.

PRO — Model a central baseline ruleset and the domains that adopt it (inherit / override / waive / defer / local rules) and compute divergence per rule, drift per domain, and local rules worth promoting.

The 77 focused topic areas of the network (agents, gateways, security, …), each a subsite with its own catalog.

Search the governance building blocks by type: guidance (177), rules (617), policies (283), standards (432), strategies (75), schema (11), properties (790), experiences (46), lifecycle (29).

Browse profiled companies (Fortune 1000 + API providers) by name; ranked by technology-readiness signal. Free.

API Evangelist Conversations — recorded discussions with API practitioners (guest, company, YouTube/SoundCloud links).

Browse the demand-side entity catalog — every service, tool and standard companies are measured against, ranked by how many carry it. Free. This is the left-hand side of the inversion: pick an entity here, then call entity_demand to see WHO.

The standards bodies API Evangelist has actually MEASURED — repositories, maturity, governance, coalition. Distinct from find_standards, which searches 613 catalog entries describing what a standard IS. Free.

API Evangelist papers — single-PDF deep dives on one practice or topic, with outlines.

Search or browse 5,100+ API Evangelist stories (2010–present); filter by year or tags.

Given any doc (type + slug), the most related content across the whole network, ranked by shared-tag relevance (rare, specific tags weigh most). "More like this," across stories, areas, guidance, papers, conversations, and more.

The services API Evangelist offers teams and customers — API strategy, governance, discovery, and evangelism engagements by Kin Lane. The front door to working with API Evangelist. (For the third-party vendor registry, use find_solutions.)

The solutions registry — 740+ third-party API services and tools (gateways, portals, testing, monitoring, …) ranked by adoption across the companies API Evangelist tracks.

Browse and rank the network tag taxonomy — every subject tag across 16k+ docs, by frequency or breadth (how many content types use it). Search with q. The map of what API Evangelist covers.

The open-source tooling registry — 400+ tools in use across the companies API Evangelist tracks, each with adoption counts and technology-radar placement.

The API Evangelist video library — interviews and discussions from across the API space, searchable by transcript.

The API vocabulary — thousands of resources, actions, personas, domains, schemas, and tags extracted from the API landscape. Filter by category.

PRO — For a code-first API: identify which OpenAPI generator produced the spec, and split findings into those to fix with code annotations vs. spec authoring, with per-generator remediation.

PRO — Propose an OpenAPI Overlay that fixes the lint errors (or the `rules` you name), apply it, re-lint, and report what was resolved, what newly fires, and any breaking change. Review the overlay before applying it.

From an OpenAPI, forge an MCP server design, per-operation tools, Agent Skills, an enriched OpenAPI, a server.json, and apis.json properties.

Choose which operations and fields an API exposes to agents and emit a governed Tyk OpenAPI, an MCP tool manifest, and a Spectral ruleset with PII and secret checks.

Generate an API's llms.txt and an AGENTS.md consumption contract — base URL, auth, the operation table, deprecated operations to avoid, and usage rules.

One topic area with its related-area graph resolved — walk the network from here.

One building block by type + slug; include=["content"] returns the full body.

Full demand-side profile for one company: 40-dimension readiness, adopted stack, per-quarter history. Pro.

Every way to reach API Evangelist — email, contact form, newsletter, GitHub, social channels, and postal mail.

One conversation with guest detail and media links; include=["content"] returns the writeup.

The static machine-readable feeds every network site publishes (JSON, APIs.json, zero-auth) — the no-key alternative to this API.

One editorial guidance section as a list: history, technology, business, politics, governance, or evangelism — the six lenses API Evangelist organizes guidance through.

PRO — Read your org default ruleset: the one every governance call without its own `ruleset` runs against.

START HERE. What the API Evangelist network offers: sixteen years of API research as searchable stories, 77 topic areas, governance building blocks (guidance, rules, policies, standards, strategies), papers, conversations, and the consulting services Kin Lane offers teams. Returns counts, entry points, and how to engage.

One paper with its full outline and purchase/landing URL.

One story by slug (YYYY-MM-DD-slug); include=["content"] returns the full markdown body.

Full detail for one service offering by slug; include=["content"] inlines the full pitch.

One solution from the vendor registry by slug, with its website and adoption count.

PRO — catalog intelligence: per-type counts, stories-per-year, and the top tags by reach across the network.

One tag with its per-type counts and everything it labels across the whole network (stories, areas, guidance, papers, …). Filter with types.

One of the four research timelines in chronological order: api (the moments that shaped web APIs), resources (which digital resources became APIs and when), industries (the industrial history framing API infrastructure), people (the people who made compute and APIs possible).

One tool from the tooling registry by slug, with its website, adoption count, and radar ring.

One video by slug with its YouTube id; include=["content"] returns the full transcript.

PRO — Run the core governance checks across a WHOLE SET of internal APIs and roll them up: per-API score/grade/errors/PII, plus estate aggregates (avg score, grade distribution, APIs with PII/secrets) and a worst-first punch-list of what to fix. Pass `apis` ([{id, document}]) and your own `ruleset`. detail:true adds per-API dimensions.

Turn Spectral findings into a self-contained HTML governance report — severity summary, grouped by rule, framed toward progress.

PRO — Curated guide to one API topic (e.g. "gateways", "api governance", "discovery", "agents"). Bundles the matching topic area (with related areas), top guidance, rules, policies, and standards, relevant papers and recent stories, plus the API Evangelist services that can help a team with this topic.

Services, tools, or standards ranked by how many companies adopt them. Free.

Cross-section ranking of the 40 tracked investment dimensions (AI, cloud, governance, …) by company signal. Free.

Lint an agent SKILL.md (markdown with YAML frontmatter) against the API Commons skill rules — name, description, structure, metadata.

Map each REST operation to its MCP tool and Agent Skill — the API -> MCP -> Agent-Skill chain — from an APIs.json, with a free/paid coverage scorecard and a flow map.

Generate an example request and success-response payload for every operation from its schema.

Evaluate a JSONPath (a rule's `given`) against a document and return what it matches — pointers, values, and optionally whether `field` is present on each match. The fastest way to get a `given` right.

Reconcile a waivers file against lint output: suppress sanctioned violations and surface the expired, stale, and expiring ones. Returns the effective failing set a build should gate on.

PRO — Turn a prose API style guide into an owned, grounded ruleset: one rule per checkable statement, each validated, with the statements no rule can check listed separately. Test the result with test_ruleset.

Score how reusable a set of APIs is and detect duplication across them — the anti-sprawl view of an estate.

Unified search across the whole network: 5k+ stories, 77 topic areas, 2.5k governance building blocks, papers, conversations, videos, tools, timelines, services, and vocabulary. Filter with types (posts, areas, guidance, rules, policies, standards, strategies, schema, properties, experiences, lifecycle, conversations, videos, papers, services, solutions, tools, timelines, vocabulary).

PRO — Store an org default ruleset (validated first). From then on validate, coverage, scorecard, estate, baseline, codefirst and fix use it whenever no `ruleset` is passed.

How far a standards body actually got: repositories published, how many graduated past unclassified and the resulting share, release cadence, contributor count — with the provenance of every figure and an explicit list of what is NOT measured. Free, because a specification is a public good.

Who is actually behind a standard: the governing bodies and their membership, the working groups, the member companies, and the named people. Carries the caveats where our machine-readable source disagrees with the body's own published roster. Free.

Every repository a standards body publishes, with maturity, stars, forks, open issues and archived status. Free.

Report something wrong with a result: wrong data, a filter that did not filter, a ranking that put off-topic results first, a number you could not reproduce, or an answer that was useless for your task. Free, and the fastest way to get a defect fixed — the support sweep reads the log this lands in. Say what you expected as well as what you got.

Run a ruleset against fixture documents with expectations — codes that must fire, exact counts, or a clean lint — and report pass/fail per case plus which rules no case asserts on or ever triggers.

Lint an OpenAPI, AsyncAPI, Arazzo, or JSON Schema document against the curated best-of-breed ruleset (Spectral) and return the findings. Pass your own `ruleset` to run rules you own instead of the catalog — which is what you should do before gating on anything.

Validate an API Onboarding Descriptor (AID) against the api-commons schema and report which optional sections it fills in.

Check that an OpenLint/Spectral ruleset is valid BEFORE running or storing it: invalid JSONPath, unknown functions, undefined aliases, and anything the engine rejects. Catalog metadata (title, prompt, x-*) is set aside and reported. Run this on every ruleset you write.

Re-verify a governance certificate against the API it attests to. If the API drifted or the certificate was forged, verification fails.