Nameko

Nameko is a microservices framework for Python that provides tools for building, testing, and running services. It supports RPC over AMQP, HTTP endpoints, WebSocket connections, and timer-based workers, with built-in dependency injection and a testing framework that allows services to be tested in isolation or integration.

Nameko is listed with 1 API on the APIs.io network. Tagged areas include AMQP, Dependency Injection, Framework, Microservices, and Python.

The Nameko catalog on APIs.io includes 1 Spectral governance ruleset.

Nameko’s developer surface includes documentation, getting-started guide, and 11 more developer resources.

📡 Profile data on GitHub

16.8/100 emerging ▬ flat Agent 1/100 human only Heartbeat 97/100 alive self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

1 API

AMQP Dependency Injection Framework Microservices Python RPC Testing

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 16.8/100 · emerging

Contract Quality 1.4 / 19

Developer Ergonomics 1.4 / 15

Access Clarity 1.2 / 15

Operational Transparency 2.6 / 10

Contract Governance 0.9 / 9

Discoverability 4.3 / 8

Regulatory Posture 0.0 / 15

Open Source Surface 5.0 / 10

Agent readiness — 1/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 75 points between them, because both conditional facets apply and carry 25 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/nameko/"><img src="https://apis.io/badge/nameko/card.svg" alt="Nameko on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 7.2 — up to +23.2 composite points
Access Clarity scores 7.9 — up to +18.4 composite points
Developer Ergonomics scores 9.5 — up to +18.1 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/nameko/apis.yml: open an issue on github.com/api-evangelist/nameko to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

AMQP

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

RPC

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Nameko

Nameko is a microservices framework for Python that provides tools for building, testing, and running services. It supports RPC over AMQP, HTTP endpoints, WebSocket connections,...

Nameko API pricing

Not yet checked against Nameko's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Nameko's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Nameko Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Nameko Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Nameko Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Nameko — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

Nameko Service Configuration

11 properties

JSON SCHEMA

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

IssueTracker

IssueTracker

Releases

Releases

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

License

License

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

PyPI

PyPI

Source (apis.yml)

aid: nameko
name: Nameko
description: Nameko is a microservices framework for Python that provides tools for building, testing, and running services.
  It supports RPC over AMQP, HTTP endpoints, WebSocket connections, and timer-based workers, with built-in dependency injection
  and a testing framework that allows services to be tested in isolation or integration.
type: Index
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/nameko.png
x-docs-platform: sphinx
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
tags:
- AMQP
- Dependency Injection
- Framework
- Microservices
- Python
- RPC
- Testing
tags_raw:
- AMQP
- Dependency Injection
- Frameworks
- Microservices
- Python
- RPC
- Testing
url: https://raw.githubusercontent.com/api-evangelist/nameko/refs/heads/main/apis.yml
created: '2026-03-26'
modified: '2026-04-28'
specificationVersion: '0.23'
apis:
- aid: nameko:nameko
  name: Nameko
  description: Nameko is a microservices framework for Python that provides tools for building, testing, and running services.
    It supports RPC over AMQP, HTTP endpoints, WebSocket connections, and timer-based workers, with built-in dependency injection
    and a testing framework that allows services to be tested in isolation or integration.
  humanURL: https://github.com/nameko/nameko
  tags:
  - AMQP
  - Dependency Injection
  - Framework
  - Microservices
  - Python
  - RPC
  - Testing
  tags_raw:
  - AMQP
  - Dependency Injection
  - Frameworks
  - Microservices
  - Python
  - RPC
  - Testing
  properties:
  - type: JSONSchema
    url: https://raw.githubusercontent.com/api-evangelist/nameko/refs/heads/main/json-schema/nameko-configuration.json
common:
- type: Plans
  url: plans/nameko-plans-pricing.yml
- type: RateLimits
  url: rate-limits/nameko-rate-limits.yml
- type: FinOps
  url: finops/nameko-finops.yml
- type: IssueTracker
  url: https://github.com/nameko/nameko/issues
- type: Releases
  url: https://github.com/nameko/nameko/releases
- type: ContributionGuide
  url: https://github.com/nameko/nameko/blob/master/docs/contributing.rst
- type: License
  name: Apache-2.0
  url: https://github.com/nameko/nameko/blob/master/LICENSE
- type: Website
  url: https://github.com/nameko/nameko
- type: Documentation
  url: https://nameko.readthedocs.io/
- type: GettingStarted
  url: https://nameko.readthedocs.io/en/stable/getting_started.html
- type: GitHubOrganization
  url: https://github.com/nameko
- type: GitHubRepository
  url: https://github.com/nameko/nameko
- type: PyPI
  url: https://pypi.org/project/nameko/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Nameko API — frequently asked questions

Does Nameko have an API?

Yes. APIs.io lists 1 API from Nameko, including Nameko.

How much does the Nameko API cost?

APIs.io lists 3 pricing plans for Nameko, with each plan's price, limits and inclusions under Pricing on this page.

Is the Nameko API ready for AI agents?

Nameko has a Kin Score of 16.8 out of 100 (emerging) and an Agent Readiness score of 0.6 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/nameko"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/nameko/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/nameko/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.