{"service":"UnifAPI","status":"not_supported","supported":false,"updated_at":"2026-06-02","covered_origins":["https://unifapi.com","https://api.unifapi.com","https://mcp.unifapi.com"],"summary":"UnifAPI does not require HTTP Message Signatures for public-data API or MCP access today. Use OAuth bearer tokens for MCP and workspace API keys for direct HTTP calls.","authentication":[{"scheme":"OAuth 2.0 Bearer","use":"Recommended for MCP clients.","resource_metadata":"https://mcp.unifapi.com/.well-known/oauth-protected-resource","docs":"https://unifapi.com/auth.md"},{"scheme":"API key bearer","use":"Fallback for direct HTTP integrations and MCP clients that require a static bearer header.","header":"Authorization: Bearer $UNIFAPI_API_KEY","docs":"https://unifapi.com/auth.md"}],"agent_behavior":["Do not generate HTTP Message Signature headers for UnifAPI unless a future directory version says supported=true.","Do not ask the user for signing keys.","Use auth.md and OAuth protected-resource metadata for credential discovery."],"links":{"auth":"https://unifapi.com/auth.md","versioning":"https://unifapi.com/versioning.md","sandbox":"https://unifapi.com/sandbox.md","status":"https://unifapi.com/status.md","contact":"https://unifapi.com/contact.md"}}