API.market
API.market (Noveum) is an API marketplace launched in April 2024 where developers discover, subscribe to and call third-party APIs and AI models with one account, one x-api-market-key and unified billing, and where sellers import an OpenAPI source, set pricing plans and get paid. The platform itself exposes a hosted MCP gateway at https://api.market/api/mcp/gateway (Streamable HTTP, OAuth 2.1 with dynamic client registration, or API key) with five tools (search_apis, get_api_tools, call_api, check_usage, manage_subscription), a Subscription Management REST API and a read-only Usage API. Individual APIs sold on the marketplace belong to their own providers and are not listed here.
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 API.market the way a machine reads it — 23 machine-readable artifacts across 15 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 — API.market scores 38.0/100 (thin), with a separate agent-readiness read of 42/100 (agent ready). 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
How this is scored →scored 2026-11-06 · rubric v0.27.0
Put this on your own site. The badge is drawn live from API.market'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/api-market/"
title="API.market on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/api-market.svg"
alt="API.market Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/api-market/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/api-market/"
title="API.market on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/api-market/card.svg"
alt="API.market Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile API.market
Each block below is one kind of artifact we hold for API.market. 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 15
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.
API.market MCP Gateway
Hosted remote MCP server (Streamable HTTP) that lets AI agents discover and call the APIs listed on API.market through five tools: search_apis, get_api_tools, call_api, check_us...
API.market Subscription Management API
REST API for reading a marketplace product and its pricing plans, reading the caller's current subscription, creating/upgrading/downgrading a subscription to a pricing plan (wit...
API.market Usage API
Read-only REST API that returns quota, calls made and renewal dates for one subscription or for all of the caller's active subscriptions. Authenticated with the x-api-market-key...
API.market API.market API
The API.market API API from API.market — 2 operation(s) for api.market api.
API.market Bridgeml API
The Bridgeml API from API.market — 2 operation(s) for bridgeml.
API.market Images API
The Images API from API.market — 2 operation(s) for images.
API.market Magicapi API
The Magicapi API from API.market — 33 operation(s) for magicapi.
API.market MCP API
The MCP API from API.market — 1 operation(s) for mcp.
API.market Models API
The Models API from API.market — 1 operation(s) for models.
API.market Pipfeed API
The Pipfeed API from API.market — 3 operation(s) for pipfeed.
API.market Predictions API
The Predictions API from API.market — 1 operation(s) for predictions.
API.market Status API
The Status API from API.market — 1 operation(s) for status.
API.market Subscription API
The Subscription API from API.market — 2 operation(s) for subscription.
API.market Toonme API
The Toonme Api API from API.market — 4 operation(s) for toonme api.
API.market User API
The User API from API.market — 3 operation(s) for user.
Scroll within the panel for all 15 ·
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.
API.market MCP Gateway
Remote MCP server at api.market over streamable HTTP requiring OAuth; 5 tools listed.
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Api Market Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Api Market Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
API.market API Rules
SPECTRALSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for API.market — 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 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/api-market · machine-readable index on apis.io
This is an independent, third-party profile of API.market, 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.