Deterministic · Pay-per-use · No guessing

AgentVerify 97 — a verification API for autonomous AI agents.

AgentVerify 97 gives autonomous agents a single JSON endpoint to confirm companies, VAT numbers, domains and documents against registered data sources. The customer is always machine — an agent that must know its counterparty before every transaction.

Contact usRead the API
Verdicts
VERIFIED · NOT_VERIFIED · UNKNOWN · NEEDS_REVIEW · PROVIDER_UNAVAILABLE · INVALID_INPUT · ERROR
Keys
Idempotent — never double-billed
Billing
Lookup-based — credits debited only when a registered source performed billable work
receipt · 0x9a14
VERIFIED

POST /api/v1/verify/company

{
  "name":    "Norden AB",
  "country": "FI",
  "idempotency_key":
    "ord_2025-04-12#c6f1"
}

200 OK — debited 1 credit

sandbox example
{
  "status":    "VERIFIED",
  "provider":  "sandbox-company",
  "latency_ms": 312,
  "raw": {
    "name":   "Norden AB",
    "status": "active"
  }
}

When the source cannot confirm — AgentVerify 97 returns UNKNOWN or PROVIDER_UNAVAILABLE, never a guess.

Features

Built for the moment an agent must know — or decline to guess.

Deterministic

No hallucinations

If a registered source cannot confirm the data, the response is always UNKNOWN or PROVIDER_UNAVAILABLE — no guesswork, no filled-in estimate. The agent always knows when it does not know.

Idempotent

No double charges

Idempotency keys prevent the same verification from being billed twice during network retries. A receipt is written only for the first successful response.

Modular

Add sources without rewrites

The verification engine and provider adapters are separated. New data sources join via a configuration change — the core stays untouched.

API

One JSON endpoint — same response, same receipt.

Every verification uses the same request shape, the same response anatomy, and the same idempotency key. No bespoke integrations, no asymmetric error codes.

  • Deterministic response anatomy — seven verdicts: VERIFIED, NOT_VERIFIED, UNKNOWN, NEEDS_REVIEW, PROVIDER_UNAVAILABLE, INVALID_INPUT, ERROR.
  • Flaky external services are bypassed with timeouts, retries and per-adapter circuit breakers.
  • Webhook events confirm settlement and persist every receipt.

POST /api/v1/verify/company

{
  "name":    "Norden AB",
  "country": "FI"
}

Response

VERIFIED
sandbox example
{
  "status":   "VERIFIED",
  "provider": "sandbox-company",
  "raw":      { "name": "Norden AB" }
}

Verdicts

Seven verdicts — and never an eighth.

AgentVerify 97 always returns exactly one of these seven. The agent reads the situation at a glance — no need to interpret exceptions or asymmetric error codes.

  • VERIFIED

    A registered source confirmed the data.

    An official or public registry returned a matching record. AgentVerify 97 deducts a credit and writes a receipt.

  • NOT_VERIFIED

    A registered source actively rejected the data.

    The source responded — and the answer was negative. The agent must not retry; the answer is negative.

  • UNKNOWN

    No registered source could confirm it.

    No public registry was able to return a match for the subject. The verdict is UNKNOWN — no guess, no filled-in estimate.

  • NEEDS_REVIEW

    Sources disagreed or returned partial evidence.

    Two or more providers returned conflicting results, or evidence is partial. The agent must escalate to a human reviewer.

  • PROVIDER_UNAVAILABLE

    The upstream service did not respond.

    A source was unreachable after its timeout window. AgentVerify 97 does not debit a credit and never returns a guessed answer.

  • INVALID_INPUT

    The request was malformed or unsupported.

    The subject did not parse, the country code was unknown, or the resource does not support this query type. No credit is debited.

  • ERROR

    The adapter itself failed.

    An internal adapter threw unexpectedly — a code bug, not an upstream issue. AgentVerify 97 returns ERROR so the agent never acts on a stale answer; operator dashboards show this status with its internal cause.

Pricing

Lookup-based billing — credits follow real provider work.

Pre-purchased credits are consumed when a registered source performed billable work — VERIFIED, NOT_VERIFIED, NEEDS_REVIEW, and UNKNOWN-with-a-real-answer all consume one credit. PROVIDER_UNAVAILABLE before any lookup, INVALID_INPUT (never reaches a provider), and ERROR (an adapter bug) consume nothing.

Sign up, start verifying

Trial
  • Free trial credits on signup
  • Same API as paying customers
  • Deterministic verdicts across all seven statuses
Contact us

Billed only on real provider work

Most popular
Pay-as-you-go
  • Credits billed only when a registered source performed billable work — VERIFIED, NOT_VERIFIED, NEEDS_REVIEW, and UNKNOWN-after-real-answer all consume; UNKNOWN-without-evidence, PROVIDER_UNAVAILABLE, INVALID_INPUT, and ERROR do not
  • Idempotent keys prevent double-billing on retries
  • Receipt stamped for every consumed credit
Request a quote

When credits run low — AgentVerify 97 refills them

Auto top-up
  • Automatic balance alerts and pre-approved top-ups
  • Refunds for failed verifications
  • Webhook events for bookkeeping and audit
Request a demo

FAQ

Frequently asked questions.

If yours isn't on the list, contact us — we usually reply within the same business day.

Ask directly

AgentVerify 97 does not infer or fill in values. If a registered source does not return a match, the verdict is UNKNOWN. If the provider itself fails, the verdict is PROVIDER_UNAVAILABLE. If the request is malformed, INVALID_INPUT. If sources disagree, NEEDS_REVIEW. If the source actively answers "no", NOT_VERIFIED. Anything else — including a positive guess — is not on this menu.

Contact us

Your agent deserves an answer it can trust as true — or an admission it cannot.

Tell us your domain and expected verification volume — we'll send a quote, the technical API details, and free trial credits the same business day.

Write agentverify97@polsia.appBack to top

mailto:agentverify97@polsia.app