API7.ai · Authentication Profile

Api7 Authentication

Authentication

Authentication schemes documented for API7.ai AISIX gateway

API7.ai declares 5 security scheme(s) across its OpenAPI definitions.

CompanyAPI GatewayAI GatewayOpen SourceCloud
Methods: Schemes: 5 OAuth flows: API key in:

Security Schemes

Bearer token (upstream) http-bearer
API key (upstream) apiKey
OAuth 2.0 client credentials (upstream) oauth2
· flows:
Gateway API key (client to AISIX) http-bearer
Gateway API key (alternative header) apiKey

Source

Authentication Profile

Raw ↑ 
generated: '2026-10-15'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.api7.ai/ai-gateway/agent-gateway/upstream-authentication.md
sources:
- https://docs.api7.ai/ai-gateway/agent-gateway/upstream-authentication.md
- https://docs.api7.ai/ai-gateway/mcp-gateway/client-authentication.md
- https://docs.api7.ai/ai-gateway/mcp-gateway/upstream-authentication.md
- https://docs.api7.ai/ai-gateway/traffic-controls/caller-api-keys.md
description: Authentication schemes documented for API7.ai AISIX gateway
schemes:
- type: http-bearer
  name: Bearer token (upstream)
  evidence: 'Authorization: Bearer <secret>'
  location: header
  header: Authorization
  how_to_obtain: 'Configured as the `secret` field of an agent or MCP server with `auth_type: "bearer"`.'
- type: apiKey
  name: API key (upstream)
  evidence: 'x-api-key: <secret>'
  location: header
  header: x-api-key
  how_to_obtain: 'Configured as the `secret` field of an agent or MCP server with `auth_type: "api_key"`.'
- type: oauth2
  name: OAuth 2.0 client credentials (upstream)
  evidence: 'Authorization: Bearer <access_token>'
  location: header
  header: Authorization
  flows:
  - client_credentials
  token_url: value of `token_url` field in the MCP server resource
  scopes:
  - mcp.read
  - mcp.write
  how_to_obtain: 'Configured with `auth_type: "oauth2"`, providing `client_id`, `token_url`, `secret`, and optional `scopes` in the MCP server
    definition.'
- type: http-bearer
  name: Gateway API key (client to AISIX)
  evidence: 'Authorization: Bearer <api key>'
  location: header
  header: Authorization
  how_to_obtain: Provided as the caller's API key (`AISIX_MCP_KEY`) and sent on each request.
- type: apiKey
  name: Gateway API key (alternative header)
  evidence: 'x-api-key: <api key>'
  location: header
  header: x-api-key
  how_to_obtain: Alternative to the bearer header for the caller's API key.
docs: https://docs.api7.ai/ai-gateway/agent-gateway/upstream-authentication.md

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact 
curl "https://apis.io/api/v1/security/api7-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

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.