ReqKey website screenshot

ReqKey

ReqKey is out-of-band API key authentication, usage credits, rate limiting and request analytics as a service for teams that sell or expose an API. It never sits in front of customer traffic: your own middleware makes one call to POST /key/validate per request, which checks the key, deducts a credit from that customer's pool and records the decision, typically in under 5ms over a reused connection. The defining design choice is that credits and rate limits live on the CONSUMER rather than the key, so issuing a customer fifty keys never multiplies their plan into fifty quotas and disabling a consumer stops all of its keys at once. Validation is Redis-backed and runs in multiple AWS regions with a global sync layer reconciling credit balances. A second endpoint, POST /ingest, correlates full request/response logs to a validation by requestId and feeds an Analytics API over two datasets. Seven first-party SDKs wrap both calls as framework middleware.

ReqKey publishes 1 API on the APIs.io network. Tagged areas include APIKeys, Authentication, Authorization, Rate Limiting, and Usage Metering.

ReqKey’s developer surface includes authentication, documentation, API reference, getting-started guide, support, engineering blog, pricing, and 20 more developer resources.

40.7/100 developing ▬ flat Agent 8/100 agent aware Front door AI 3/6 light saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
AccessFreemiumSelf serve⚡ Free to try
1 APIs
APIKeysAuthenticationAuthorizationRate LimitingUsage MeteringAPI AnalyticsAPI ManagementDeveloper ToolsMiddlewareObservability

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
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.
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 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
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 github.com/api-evangelist/reqkey: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

ReqKey REST API

REST API for API key management, usage credits/metering, rate limiting, and traffic analytics. POST/JSON endpoints authenticated with a project root key via Bearer token; single...

Pricing Plans 1

Published pricing tiers and plan structures.

Reqkey Plans

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Reqkey Rate Limits

6 limits

RATE LIMITS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Reqkey Authentication

http · 1 scheme

SECURITY

Reqkey Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Reqkey Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
name: ReqKey
description: 'ReqKey is out-of-band API key authentication, usage credits, rate limiting and request analytics as a service
  for teams that sell or expose an API. It never sits in front of customer traffic: your own middleware makes one call to
  POST /key/validate per request, which checks the key, deducts a credit from that customer''s pool and records the decision,
  typically in under 5ms over a reused connection. The defining design choice is that credits and rate limits live on the
  CONSUMER rather than the key, so issuing a customer fifty keys never multiplies their plan into fifty quotas and disabling
  a consumer stops all of its keys at once. Validation is Redis-backed and runs in multiple AWS regions with a global sync
  layer reconciling credit balances. A second endpoint, POST /ingest, correlates full request/response logs to a validation
  by requestId and feeds an Analytics API over two datasets. Seven first-party SDKs wrap both calls as framework middleware.'
url: https://raw.githubusercontent.com/api-evangelist/reqkey/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
image: https://www.reqkey.com/og-image.png
created: '2026-07-26'
modified: '2026-08-09'
specificationVersion: '0.23'
tags:
- APIKeys
- Authentication
- Authorization
- Rate Limiting
- Usage Metering
- API Analytics
- API Management
- Developer Tools
- Middleware
- Observability
tags_raw:
- api-keys
- authentication
- authorization
- rate-limiting
- usage-metering
- api-analytics
- api-management
- developer-tools
- middleware
- observability
apis:
- name: ReqKey REST API
  description: REST API for API key management, usage credits/metering, rate limiting, and traffic analytics. POST/JSON endpoints
    authenticated with a project root key via Bearer token; single unauthenticated GET /health.
  humanURL: https://www.reqkey.com/docs
  baseURL: https://api.reqkey.com
  tags:
  - APIKeys
  - Authentication
  - Authorization
  - Rate Limiting
  - Usage Metering
  - API Analytics
  - API Management
  - Developer Tools
  - Middleware
  - Observability
  tags_raw:
  - api-keys
  - authentication
  - authorization
  - rate-limiting
  - usage-metering
  - api-analytics
  - api-management
  - developer-tools
  - middleware
  - observability
  properties:
  - type: Documentation
    url: https://www.reqkey.com/docs
  - type: LLMSTxt
    url: https://www.reqkey.com/llms.txt
maintainers:
- FN: ReqKey Support
  email: support@reqkey.com
  url: mailto:support@reqkey.com
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 90
  at: '2026-07-26T12:34:37.893Z'
x-enrichment:
  date: '2026-08-09'
  status: enriched
  artifacts_added: 14
  pass: local-v1
  contract_discovery:
    openapi: not-published
    graphql: not-published
    asyncapi: not-published
    mcp: not-published
    agent_card: not-published
    postman: not-published
    note: Probed /openapi.json, /openapi.yaml, /swagger.json, /v1/openapi.json, /api-docs, /docs, /redoc on api.reqkey.com
      and www.reqkey.com (all 404), every /.well-known/ path on all three hosts (all 404), mcp.reqkey.com (no DNS), and the
      full recursive file tree of all seven github.com/Req-Key SDK repositories. ReqKey's machine-readable surface is a 26KB
      llms.txt and nothing else; the API reference is complete, server-rendered HTML with no spec behind it.
common:
- type: X-MCPServerCandidate
  url: mcp/reqkey-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DomainSecurity
  url: security/reqkey-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/reqkey-vulnerability-disclosure.yml
- type: Authentication
  url: authentication/reqkey-authentication.yml
- type: ErrorCatalog
  url: errors/reqkey-problem-types.yml
- type: Conventions
  url: conventions/reqkey-conventions.yml
- type: Conformance
  url: conformance/reqkey-conformance.yml
- type: Lifecycle
  url: lifecycle/reqkey-lifecycle.yml
- type: DataModel
  url: data-model/reqkey-data-model.yml
- type: RateLimits
  url: rate-limits/reqkey-rate-limits.yml
- type: Plans
  url: plans/reqkey-plans.yml
- type: Packages
  url: packages/reqkey-packages.yml
- type: SDKs
  url: packages/reqkey-packages.yml
- type: LLMsTxt
  url: llms/reqkey-llms.txt
- type: Documentation
  url: https://www.reqkey.com/docs
- type: APIReference
  url: https://www.reqkey.com/docs/api/keys
- type: GettingStarted
  url: https://www.reqkey.com/docs/how-it-works
- type: Support
  url: https://www.reqkey.com/contact
- type: Blog
  url: https://www.reqkey.com/blog
- type: GitHubOrganization
  url: https://github.com/Req-Key
- type: Pricing
  url: https://www.reqkey.com/pricing
- type: SignUp
  url: https://www.reqkey.com/sign-in?mode=signup
- type: Login
  url: https://www.reqkey.com/sign-in
- type: TermsOfService
  url: https://www.reqkey.com/legal/terms
- type: PrivacyPolicy
  url: https://www.reqkey.com/legal/privacy
- type: Website
  url: https://www.reqkey.com
- type: LinkedIn
  url: https://www.linkedin.com/company/reqkey

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/reqkey"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/reqkey/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/reqkey/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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