ffpipe · Authentication Profile

ffpipe Authentication

Authentication

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

MediaPaymentsVideoAutomation
Methods: apiKey Schemes: 2 OAuth flows: API key in: header

Security Schemes

x402 apiKey
· in: header (payment-signature)
retryVoucher apiKey
· in: header (x-retry-voucher)

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-07'
method: derived
source: openapi/ffpipe-dev-openapi.json
summary:
  types:
  - apiKey
  api_key_in:
  - header
schemes:
- name: x402
  type: apiKey
  in: header
  parameter: payment-signature
  description: 'Not an API key: an x402 v2 payment payload, freshly signed per request from
    the PAYMENT-REQUIRED challenge. Modelled as apiKey because OpenAPI has no x402 security
    type — see the `x-x402` extensions.'
  sources:
  - openapi/ffpipe-dev-openapi.json
- name: retryVoucher
  type: apiKey
  in: header
  parameter: x-retry-voucher
  description: Single-use retry credential issued when a paid job failed on our side.
  sources:
  - openapi/ffpipe-dev-openapi.json

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/ffpipe-dev-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.