InCountry · Authentication Profile

Incountry Authentication

Authentication

InCountry secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyData ResidencyData LocalizationCompliancePrivacyData SecurityEncryptionPIIGDPRData SovereigntyMCP
Methods: oauth2 Schemes: 1 OAuth flows: clientCredentials API key in:

Security Schemes

OAuth2ClientCredentials oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://docs.incountry.com/rest-api/
docs: https://docs.incountry.com/rest-api/
summary:
  types: [oauth2]
  oauth2_flows: [clientCredentials]
  token_lifespan_seconds: 300
schemes:
- name: OAuth2ClientCredentials
  type: oauth2
  flow: clientCredentials
  token_url: https://idp.incountry.com/oauth2/token/
  grant_type: client_credentials
  client_auth: HTTP Basic (Base64 of Client ID:Client Secret)
  audience: REST API and PoP API addresses (per-environment)
  scope: Environment ID (UUID) — an environment identifier, not a named permission scope
  token_lifespan_seconds: 300
  notes: >-
    Client ID and Client Secret are generated by creating a REST API integration
    in the InCountry Portal. Access tokens are short-lived (300s) and must be sent
    as a Bearer token on data-communication requests. Payloads are additionally
    encrypted with AES-GCM (256-bit key, 96-bit nonce).
mcp_authentication:
  product: AgentCloak MCP server
  header: x-inc-agentcloak-api-key
  format: "<mcp_server_uuid>:<secret>"