Refuel · Authentication Profile

Refuel Ai Authentication

Authentication

Refuel secures its APIs with http across 2 declared security schemes, as derived from its OpenAPI definitions.

Artificial IntelligenceLLMData LabelingData EnrichmentAutolabelMachine-LearningData QualityTraining DataFine-TuningData TransformationEntity ResolutionContent Moderation
Methods: http Schemes: 2 OAuth flows: API key in: header

Security Schemes

HTTPBearer http
scheme: bearer
BearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑
generated: '2026-08-14'
method: searched
source: openapi/refuel-ai-applications-api-openapi.yml, openapi/refuel-ai-cloud-api-openapi.yml
docs: https://docs.refuel.ai/sdk/python
summary:
  types:
  - http
  api_key_in:
  - header
  oauth2_flows: []
schemes:
- name: HTTPBearer
  type: http
  scheme: bearer
  description: >-
    A Refuel API key sent as an HTTP Bearer token: `Authorization: Bearer <REFUEL_API_KEY>`.
    One key per team; it is issued in the Refuel app. Refuel's own catalog documentation
    shows it in use against the label endpoint, and the Python SDK reads it from the
    REFUEL_API_KEY environment variable (or an `api_key` init option).
  sources:
  - openapi/refuel-ai-cloud-api-openapi.yml
  - openapi/refuel-ai-applications-api-openapi.yml
  - https://docs.refuel.ai/sdk/python
  applied_to: '99 of 108 operations in the Cloud API spec declare a HTTPBearer security requirement'
- name: BearerAuth
  type: http
  scheme: bearer
  description: >-
    The same credential, under the scheme name used in the older
    refuel-ai-applications-api-openapi.yml. Not a second mechanism.
  sources:
  - openapi/refuel-ai-applications-api-openapi.yml
  alias_of: HTTPBearer
key_management:
  issuance: In the Refuel app (https://app.refuel.ai) per team.
  rotation: Not documented.
  expiry: Not documented.
  scopes: none — the key is all-or-nothing across the team's data.
  exposure_note: >-
    The TeamSchema component includes `api_key` and `api_key_sha`, so
    `GET /team` returns the team's own API key in the response body. Any caller (or agent)
    with the key can re-read the key. Recorded as a governance fact for anyone delegating
    Refuel access to an agent — see agentic-access/refuel-ai-agentic-access.yml.
unauthenticated_behaviour:
  status: 401
  body: '{"message":"Unauthorized"}'
  scope: >-
    Every path on cloud-api.refuel.ai except `/` and `/openapi.json` — including
    `/.well-known/*`, `/docs`-adjacent paths and `/mcp`. Probed 2026-08-14.
  note: No operation in the spec declares a 401 response, despite this being the universal behaviour.
not_supported:
- oauth2
- openIdConnect
- mutualTLS
- apiKey-in-query
- basic-auth

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/refuel-ai-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

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

Get an API key

Free tier, no email required.

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