Skip to content

Costs, limits and recovery

Start with GET /.well-known/api-catalog on the API host. This public RFC 9727 linkset points to the customer OpenAPI contract, MCP, A2A and this guide. GET /apis.json supplies a provider-authored discovery index. GET /v1/integration-policy exposes the operating facts below as JSON, without credentials or customer-specific terms. Metadata access does not authorize API execution.

Review the terms of service and privacy policy. Use OAuth for delegated agents and API keys for trusted services. Start with the smallest grant; scope authorization does not replace required user approval for a billable or mutating action. Use the field catalog before constructing a request, and inspect current account capacity before execution. A successful validation is not a reservation or permission to spend.

Metronome customer contracts and rate cards; public metadata is descriptive, not a second price authority.

Stripe for native collection; other supported source routes retain their own collection rail.

USD

Create an account, satisfy the account agreement and capacity requirements, and use an appropriately scoped credential. OAuth requires user consent; metadata discovery does not grant access.

Use authenticated field pricing and a delivery estimate where supported. Matching validation does not estimate price. Negotiated rates and contract details are never published here.

OAuth client registration identifies an application; delegated tokens remain tied to user-approved scopes and the intended resource. A suggested next action is not user approval. Revoke an unwanted connection in account settings.

Usage event Quantity property Aggregation
platform_match matched_records SUM
audience_delivery billable_records SUM
delivery_destination billable_records SUM
enrichment_field_delivery billable_records SUM
Operation / scope Usage and state Recovery
POST /v1/match/validate · discovery No customer usage; request shape and effective row IDs only. No matching, billing reservations, durable writes or input echo. Authentication/session security bookkeeping and in-memory rate limiting still apply. Correct issues and validate again. A successful validation is not execution eligibility or a price guarantee.
POST /v1/quote · discovery An expected delivery estimate and maximum estimate, not a matching quote or binding price. Saves a pending quote and replaces the audience current quote reference; does not purchase or deliver records. Review expected and maximum estimates for the exact audience/version/fields/output. Do not treat re-quoting as an identical read.
POST /v1/match · creator Real matching and enrichment can incur usage under the account agreement. Starts matching and billing work; may create a requested temporary segment. Use the same Idempotency-Key and identical payload when retrying an uncertain request. Never invent a new key to resolve a timeout. Inspect match history; validation does not reserve capacity.
POST /v1/match/file · creator Real matching and subsequent delivery can incur usage under the account agreement. Creates upload/segment workflow state; uploading and confirmed mappings can start asynchronous work. Use the same Idempotency-Key and identical payload for an uncertain creation. Inspect the existing job. Staged mapping cancellation retains the segment and is not cancellation of already-running work.
POST /v1/audiences/{id}/deliveries · creator Can purchase licensed records and incur enrichment/destination usage. Creates durable asynchronous export work and can release data outside the platform. Review the exact quote and obtain approval before execution. Inspect delivery status after a timeout; a wait timeout or archival does not cancel an in-flight delivery or retract exported data.
PATCH /v1/segments/{id} · creator Archival is not a refund. Changes availability while retaining history; restoration is subject to current object eligibility. MCP archive_segment with restore=true restores an eligible archived segment. Pending custom publication and expired custom membership have additional restrictions.
PATCH /v1/audiences/{id} · creator Archival is not a refund. Changes availability while retaining history; in-flight deliveries can continue. MCP archive_audience with restore=true restores an eligible archived audience. Restoration cannot undo prior data egress.

POST /v1/match/validate accepts the same JSON body shape as microbatch matching, under discovery scope. It checks request shape and effective row-ID uniqueness without matching, BigQuery access, durable writes or billing. Invalid input returns 400 MATCH_INPUT_INVALID with issue paths/codes; identity data is not echoed. Successful validation returns valid: true, billable: false, a record count and explicit not_checked items. Identity existence, live output-field/template availability, execution eligibility and cost are not checked. Normal authentication/session security bookkeeping and in-memory rate limiting still apply. It does not validate uploaded files.

For a network timeout on an idempotent operation, preserve the original key and identical payload. Do not create a new request ID just to escape an in-progress response. Read operation status before attempting a replacement. Idempotency support is operation-specific; consult the endpoint rather than assuming all writes are replay-safe.

An A2A task cancellation marks that task canceled and best-effort aborts its agent invocation. A downstream durable match or delivery may already exist and continue. Inspect its own status. Archive/restore changes object availability; neither action refunds usage, cancels an in-flight export nor retracts previously downloaded data.

Best-effort per-organization sliding window held per Core instance, not a distributed guaranteed quota or a financial ceiling. First-party web/internal traffic is exempt; some endpoints have separate IP limits.

Tier Requests/minute per instance
paygo 50
pilot 100
growth 500
scale 1000
enterprise 2000

Response headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Window, Retry-After.

For 429, honor Retry-After seconds and use bounded backoff with jitter. Retry writes only when that operation explicitly supports replay with a stable key. For 400/403, correct the request or grant; for 402, resolve capacity rather than automatically retrying.

Use the structured code for recovery where returned. Authentication/middleware errors may contain only error. For request validation or scope errors, correct the request or authorization instead of retrying unchanged. Resolve insufficient capacity with the account administrator. A billing estimate is not a final invoice.

Check the service status and contact support with the operation ID and non-sensitive error details. Do not send credentials or raw customer identity inputs in support reports.

The public product repository contains published contracts and release material. No fixed deprecation notice period is promised here. The OpenAPI contract describes supported request/response behavior; the operating policy adds recovery guidance, not new permissions or commercial terms.