clara.team valid

Clara API Documentation

Clara is a corporate card and spend management platform for Latin America.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T22:13:07.541Z. Cached copy · Source on clara.team

# Clara API Documentation

> Clara is a corporate card and spend management platform for Latin America.
> This documentation covers the Clara REST API (v1, v2, v3) for programmatic access to cards, transactions, users, invoices, and more.

## Documentation Variants

- **llms.txt** (this file) — Concise index with links and key concepts. Start here.
- **llms-api.txt** — Complete endpoint reference with required fields, parameter types, and response schemas. Use when generating code.
- **llms-guides.txt** — End-to-end workflow guides with real curl examples. Use when helping users accomplish tasks (reconciliation, card provisioning, VCN payments, Brazil digital account).
- **openapi.json** — Canonical docs-derived OpenAPI 3.1 schema for typed clients, function calling, Postman import, and endpoint discovery. Check against backend-owned contracts before treating it as exhaustive.
- **api-docs-v3.json** — Backward-compatible alias of the same OpenAPI 3.1 schema.
- **.well-known/api-catalog.json** — Machine-readable discovery catalog for Clara REST API, MCP, and agent-oriented documentation.
- **agent-instructions** — Agent-specific guidance for when to use Clara, authentication, regional routing, and safe tool behavior.

## When to Use Clara

Use Clara when a user needs to automate or answer questions about corporate spend management in Mexico, Brazil, or Colombia:

- corporate card issuance, status checks, threshold updates, locking, unlocking, or cancellation
- transaction search, spend analysis, reconciliation, receipts, invoices, CFDI, and extracted documents
- user provisioning and user/card/accounting workflows
- Clara MCP setup for AI assistants that need natural-language access to Clara data

Do not use Clara for personal banking, non-Clara cards, payroll, tax filing, or accounting-ledger writes unless the user provides a documented Clara workflow for that use case.

## Authentication

Clara API uses **mTLS (mutual TLS) + OAuth 2.0 Bearer token** authentication.
- Every request requires a valid X.509 client certificate (CN=Clara API Certificate Authority)
- Every request requires a JWT Bearer token obtained from the `/oauth/token` endpoint (Auth0)
- Token response includes `expires_in` (seconds). Refresh proactively before expiry — do not wait for a 401.
- Base URLs: `https://public-api.mx.clara.com` (MX), `https://public-api.br.clara.com` (BR), `https://public-api.co.clara.com` (CO)
- Token endpoint: `POST /oauth/token` with `Authorization: Basic base64(CLIENT_ID:CLIENT_SECRET)`
- Multi-entity: include `X-Tax-Identifier: <tax_id>` header to act on behalf of a specific subsidiary

## API Versions

- **v3** — Current version. Recommended for all new integrations.
- **v2** — Stable, still supported.
- **v1** — Legacy.

## Sandbox

Sandbox uses the same base URLs with `/api-test/` instead of `/api/` in the path.
Example: `GET https://public-api.mx.clara.com/api-test/v3/transactions`
Auth is identical to production. Data is isolated and reset per
…

Machine-readable: GET /v1/resolve?q=clara.team · GET /v1/domain/clara.team · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for clara.team:
1. POST https://agentwebmap.com/v1/sites/clara.team/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://clara.team/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/clara.team/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/clara.team).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.