# Pactrum auth.md

How agents authenticate with https://pactrum.com.

## Public, no authentication

These are open to any agent and need no key, account or token. They are read-only, contain no personal data, are cached for a few minutes, and are rate limited per IP.

- REST catalogue API: `https://pactrum.com/api/public/` (OpenAPI: `https://pactrum.com/openapi.json`)
- MCP server (Streamable HTTP): `https://pactrum.com/mcp`
- A2A agent: `https://pactrum.com/a2a` (card: `https://pactrum.com/.well-known/agent-card.json`)
- Markdown pages: send `Accept: text/markdown` to any public page
- `https://pactrum.com/llms.txt`, `https://pactrum.com/llms-full.txt`

## Customer account API (human sign-in only)

`https://pactrum.com/api/account/*` returns a signed-in customer's own orders. It accepts a **Firebase Authentication ID token** as `Authorization: Bearer <token>`.

- Token issuer: `https://securetoken.google.com/pactrum-ef33e` (audience `pactrum-ef33e`, RS256)
- Signing keys (JWKS): `https://www.googleapis.com/service_accounts/v1/jwk/securetoken@system.gserviceaccount.com`
- Issuer metadata: `https://securetoken.google.com/pactrum-ef33e/.well-known/openid-configuration`
- Protected resource metadata (RFC 9728): [https://pactrum.com/.well-known/oauth-protected-resource](https://pactrum.com/.well-known/oauth-protected-resource)

Tokens are issued only when the customer signs in themselves at `https://pactrum.com/login` (email and password, Google, or phone one-time code). Pactrum does not run its own OAuth authorization server or define API scopes (the token just needs the standard `openid`/`email` identity claims), and offers **no agent registration, client credentials or API keys**. Agents must not create accounts, sign in, place orders or pay on a customer's behalf.

## Staff and admin

Admin, manager and staff tools are private, use separate server-side sessions, and are not available to agents.

## Contact

info@pactrum.com · +91 99745 47999
