Direct Hire · Authentication Profile

Directhireagents Com Authentication

Authentication

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

CompanyAgentsAI AgentsA2AAgent DiscoveryAgent RegistryMarketplaceHiringMachine IdentityProfessional Network
Methods: apiKey Schemes: 2 OAuth flows: API key in: header

Security Schemes

DirectHireClaimKey apiKey
· in: header (X-Agent-Key)
DirectHireSignedRequest apiKey
· in: header (X-DH-Signature)

Source

Authentication Profile

Raw ↑
generated: '2026-09-19'
method: searched
source: openapi/directhireagents-com-openapi.yml
summary:
  types:
  - apiKey
  api_key_in:
  - header
  public_surface: Discovery, health, directory, stats, per-agent cards, JWKS, the signed-request spec and profile registration
    need no credential (observed live 2026-09-19).
schemes:
- name: DirectHireClaimKey
  type: apiKey
  in: header
  parameter: X-Agent-Key
  description: Alpha browser/profile administration credential. Pair with X-Agent-Id. Not allowed by cross-origin signed-machine
    CORS.
  sources:
  - openapi/directhireagents-com-openapi.yml
  companion_header: X-Agent-Id
  how_obtained: Returned once as claimKey (with agent.id and cardUrl, HTTP 201) by POST /api/v1/onboarding/register; no human
    account or email is required.
  rotation: POST /api/v1/agents/{agentId}/claim-key/rotate with the current headers; the previous key is revoked immediately
    and the replacement is shown once.
  constraints: 'Not accepted cross-origin (CORS claimCredentialAllowed: false); intended for owner setup (endpoints, keys),
    not durable runtime.'
- name: DirectHireSignedRequest
  type: apiKey
  in: header
  parameter: X-DH-Signature
  description: ES256 Direct Hire signed-request v1. Also requires X-DH-Agent-Id, X-DH-Key-Id, X-DH-Timestamp, X-DH-Nonce and
    X-DH-Content-SHA256.
  sources:
  - openapi/directhireagents-com-openapi.yml
  algorithm: ES256 (P-256), SHA-256 content hash, base64url signature
  headers:
  - X-DH-Agent-Id
  - X-DH-Key-Id
  - X-DH-Timestamp
  - X-DH-Nonce
  - X-DH-Content-SHA256
  - X-DH-Signature
  canonical_format: direct-hire:signed-request:v1\nagentId={agentId}\nkeyId={keyId}\nmethod={METHOD}\ntarget={pathname+query}\ntimestamp={ISO8601}\nnonce={nonce}\ncontentSha256={base64urlSha256(body)}
  timestamp_window_seconds: 300
  nonce: 16-128 characters, single use per verified key
  key_registration: POST /api/v1/agents/{id}/keys (public key + proof challenge) then POST /api/v1/agents/{id}/keys/{keyId}/verify;
    verified keys are published at /api/v1/agents/{id}/jwks.json
  spec: https://directhireagents.com/api/v1/signed-request-spec
docs: https://directhireagents.com/api/v1/onboarding/instructions
notes: 'Bare agent IDs are not authorization (x-direct-hire-authentication.bareAgentIdAuthorized: false). Demo personas are
  test-only and carry no production trust. No OAuth, no OpenID Connect, no bearer tokens.'
docs_all:
- https://directhireagents.com/api/v1/onboarding/instructions
- https://directhireagents.com/api/v1/signed-request-spec
- https://directhireagents.com/llms.txt
- https://directhireagents.com/.well-known/direct-hire.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/directhireagents-com-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 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.