One key · eleven APIs · v1

APIs that make your software smarter.

One API key. Multiple business intelligence APIs. Reconcile numbers, verify data, match entities, detect anomalies, and find revenue leaks.

First request in under 60 seconds · 1,000 records free · no credit card

POST /v1/reconcile
curl https://api.zapitra.com/v1/reconcile \
  -H "Authorization: Bearer zap_live_••••••" \
  -H "Content-Type: application/json" \
  -d '{"source_a":{"name":"crm","records":[{"email":"acme@example.com","amount":12500,"status":"won"},{"email":"globex@example.com","amount":8000,"status":"won"}]},"source_b":{"name":"billing","records":[{"email":"acme@example.com","amount":11840,"status":"paid"},{"email":"globex@example.com","amount":8000,"status":"paid"}]},"matching":{"primary_keys":["email"],"compare_fields":["amount","status"],"amount_field":"amount"}}'
ready

Choose your API.

Every endpoint takes JSON and returns structured, evidence-backed results. One key unlocks all of them.

POST/v1/reconcile

RECONCILE

Do these numbers match?

{
  "expected": 12500,
  "actual": 11840
}
POST/v1/verify

VERIFY

Can this data be trusted?

{
  "claim": "Invoice was paid in full",
  "evidence": [
    "Payment of $11,840 received"
  ]
}
POST/v1/revenue-leak

LEAK

Where did the money disappear?

{
  "orders": [
    {
      "id": "SO-1",
      "total": 12500
    }
  ],
  "invoices": [
    {
      "id": "INV-1",
      "total": 11840
    }
  ]
}
POST/v1/match

MATCH

Are these records the same thing?

{
  "left": {
    "customer_name": "Acme Incorporated",
    "email": "billing@acme.com"
  },
  "right": {
    "customer_name": "ACME Inc.",
    "email": "billing@acme.com"
  }
}
POST/v1/anomalies

DETECT

What looks unusual?

{
  "records": [
    {
      "amount": 100
    },
    {
      "amount": 105
    },
    {
      "amount": 98000
    }
  ]
}
POST/v1/normalize

NORMALIZE

Turn messy data into usable data.

{
  "data": {
    "company": " ACME, INC. ",
    "amount": "$1,245.00",
    "date": "9/6/26"
  }
}

Try Zapitra.

Pick an API, edit the request, hit run. This calls the exact production engine through a public demo endpoint — no signup, no key, not metered.

Request body (editable)
Response
// Press “Run” to send this request.

Demo endpoint · no signup · rate-limited · not metered · runs the exact production engine.

First API request in under 60 seconds.

Built for developers who would rather make an API call than book a demo.

  1. 01

    Create your account

    Sign up with email. No sales call, no onboarding questionnaire.

  2. 02

    Copy your API key

    A live key is waiting in your dashboard the moment you land.

  3. 03

    Send a request

    Paste the curl command. Swap in your data. Hit enter.

  4. 04

    Read the response

    Structured JSON with evidence and confidence. You’re live.

Playful brand. Serious infrastructure.

Built for software, not slide decks. Here is what actually backs every request.

Bearer key auth

Every request authenticates with a secret API key. Keys are hashed at rest and shown once.

Encrypted in transit

All traffic is served over HTTPS/TLS. Your payloads never travel in the clear.

Per-plan rate limits

Org-level burst limits are enforced across every instance, with clear 429 responses.

Request IDs

Every response carries a request ID so you can trace and reference any call.

Deterministic core

Reconciliation, matching, and verification run deterministic engines — same input, same output.

Versioned API

All endpoints live under /v1. We won’t break your integration out from under you.

One allowance. Every API.

Pricing is based on records processed per month, shared across all four APIs. Start free and upgrade when you need more volume.

See full pricing

Free

$0

1,000 records / month

Developer

$19/mo

10,000 records / month

Pro

$49/mo

50,000 records / month

Growth

$149/mo

250,000 records / month

Scale

$399/mo

1,000,000 records / month

Enterprise

Custom

Custom volume