filedone · Authentication Profile

filedone Authentication

Authentication

filedone declares 2 security scheme(s) across its OpenAPI definitions.

PDFImage ProcessingDocument ConversionOCRAI ToolsFile CompressionMCPProductivity

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

oauth2 oauth2

· flows:

bearer_api_key http

scheme: bearer

Source

Authentication Profile

generated: '2026-11-07'
method: searched
source: https://filedone.ai/developers
sources:
- https://filedone.ai/developers
- https://api.filedone.ai/.well-known/oauth-protected-resource
- https://api.filedone.ai/.well-known/oauth-authorization-server
- https://api.filedone.ai/mcp/server-card
docs: https://filedone.ai/developers
name: filedone authentication
summary: >-
  filedone's remote MCP server at https://api.filedone.ai/mcp accepts one of
  two credentials. The standard flow is OAuth 2.1 with PKCE: the server
  advertises OAuth 2.0 Protected Resource Metadata (RFC 9728) at
  /.well-known/oauth-protected-resource and an authorization server at
  https://api.filedone.ai, which supports Dynamic Client Registration
  (RFC 7591), Client ID Metadata Documents, and PKCE with S256. Alternatively
  a request may carry "Authorization: Bearer fdk_<key>" with an API key
  minted from the signed-in user's account page. An account can hold up to
  five keys and a key is shown exactly once.
schemes:
- name: oauth2
  type: oauth2
  flows:
    authorizationCode:
      authorization_url: https://api.filedone.ai/oauth/authorize
      token_url: https://api.filedone.ai/oauth/token
      registration_url: https://api.filedone.ai/oauth/register
      revocation_url: https://api.filedone.ai/oauth/revoke
      grant_types:
      - authorization_code
      - refresh_token
      response_types:
      - code
      code_challenge_methods:
      - S256
      token_endpoint_auth_methods:
      - none
      scopes:
      - tools:run
      - offline_access
      pkce: required
      dynamic_client_registration: true
      client_id_metadata_document: true
  evidence: https://api.filedone.ai/.well-known/oauth-authorization-server
- name: bearer_api_key
  type: http
  scheme: bearer
  bearer_format: fdk_<opaque>
  description: >-
    API key issued on the user's filedone account page under "API keys".
    Sent as "Authorization: Bearer fdk_your_key". Keys are shown once; an
    account may hold up to five at a time and can revoke a key from the
    account page.
  evidence: https://filedone.ai/developers
protected_resource_metadata: https://api.filedone.ai/.well-known/oauth-protected-resource
mcp_endpoint: https://api.filedone.ai/mcp
notes:
- The protected-resource metadata lists bearer_methods_supported = ["header"]
  only; credentials are never accepted on the query string.
- The authorization server's token endpoint uses token_endpoint_auth_method
  "none" (a public client with PKCE).

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/filedone-ai-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.