Audit roaming charges API
Recalculate international roaming charges from caller-supplied usage, tariff rules, packages, country zones, and billed charges. A usage row is priced only when exactly one tariff matches. Missing or ambiguous tariffs are reported and never assumed. Daily-pass packages zero incremental usage. Positive actual-minus-expected deltas form estimated overbilling by currency. No FX conversion is applied.
The Audit roaming charges operation is part of the Telecom Roaming Audit API on BRAINIAC.software. Recalculate international roaming charges from caller-supplied usage, tariff rules, packages, country zones, and billed charges. A usage row is priced only when exactly one tariff matches. Missing or ambiguous tariffs are reported and never assumed. Daily-pass packages zero incremental usage. Positive actual-minus-expected deltas form estimated overbilling by currency. No FX conversion is applied. It is exposed as POST /api/v1/telecom-billing/roaming-charge-audit and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied roaming usage, tariffs, packages, zones, and billed charges processed locally Limitations: A usage row is priced only when exactly one tariff matches type, country or zone, and effective dates. Missing tariff rules are not invented. Ambiguous matches are not silently chosen. No FX conversion is performed across currencies. No carrier CDR feed or rating engine is contacted. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include the other resources on the product page. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/telecom-billing/roaming-charge-auditExample request
curl -i -X POST "https://www.brainiac.software/api/v1/telecom-billing/roaming-charge-audit" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"usage": [
{
"id": "u1",
"type": "data",
"country": "FR",
"started_at": "2026-11-05T10:00:00.000Z",
"units": 5000000,
"unit_kind": "bytes"
},
{
"id": "u2",
"type": "call",
"country": "DE",
"started_at": "2026-11-05T11:00:00.000Z",
"units": 120,
"unit_kind": "seconds"
},
{
"id": "u3",
"type": "sms",
"country": "FR",
"started_at": "2026-11-05T12:00:00.000Z",
"units": 2,
"unit_kind": "messages"
}
],
"zones": [
{
"zone": "eu",
"country": "FR"
},
{
"zone": "eu",
"country": "DE"
}
],
"tariffs": [
{
"id": "tf-data",
"type": "data",
"zone": "eu",
"currency": "EUR",
"rate_per_unit": 1,
"unit_kind": "bytes",
"effective_from": "2026-01-01",
"daily_cap": 2000000
},
{
"id": "tf-call",
"type": "call",
"country": "DE",
"currency": "EUR",
"rate_per_unit": 5,
"unit_kind": "seconds",
"effective_from": "2026-01-01"
}
],
"packages": [
{
"id": "pass-fr",
"type": "daily_pass",
"country": "FR",
"currency": "EUR",
"price": 500,
"effective_from": "2026-01-01"
}
],
"billed_charges": [
{
"id": "b1",
"usage_id": "u1",
"type": "data",
"country": "FR",
"currency": "EUR",
"amount": 1000,
"billed_at": "2026-11-06T00:00:00.000Z"
},
{
"id": "b2",
"usage_id": "u2",
"type": "call",
"country": "DE",
"currency": "EUR",
"amount": 900,
"billed_at": "2026-11-06T00:00:00.000Z"
},
{
"id": "b3",
"usage_id": "u2",
"type": "call",
"country": "DE",
"currency": "EUR",
"amount": 900,
"billed_at": "2026-11-06T00:01:00.000Z"
},
{
"id": "b4",
"package_id": "pass-fr",
"type": "daily_pass",
"country": "FR",
"currency": "EUR",
"amount": 500,
"billed_at": "2026-11-05T23:00:00.000Z"
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.