Skip to main content

​
What Beltic Does

Beltic provides programmable infrastructure for verifying the entities that matter to your business — people, companies, and AI agents. Everything in Beltic is built around the Workflow API. A workflow is a pipeline of blocks — discrete verification steps like document checks, liveness, sanctions screening, and business lookups — that you configure once in the Console and trigger with a single API call. Beltic runs the blocks, handles retries and parallel execution, and returns the full block-by-block output. Credentialing is one of those blocks. When you add a credential_issue block to your workflow, Beltic takes the verified output of the preceding blocks and mints a signed JWT-VC from it — a cryptographic artifact that encodes what was verified, who was verified, and when. That credential can be stored, forwarded to partners, and verified at every future transaction point without re-running the workflow. Not every customer needs the full workflow. If you already have your own verification process — your own KYC provider, your own document stack, your own risk engine — you can skip the workflow entirely and call the Credentials API directly. Send Beltic the data you’ve already collected, and Beltic wraps it in a signed, portable credential. You get the cryptographic trust layer without changing your existing pipeline. Two patterns, same result:
PatternWhen to use
Workflow + credential blockYou want Beltic to run the verification and issue the credential in one call
Direct credential issuanceYou have your own verification process and want to attach the result to a Beltic credential

​
Quickstart

​
1. Get an API key

Create an account at console.beltic.com, navigate to Settings → API Keys, and create a key with workflows:execute scope. Use a sk_staging_... key while testing.

​
2. Execute a workflow

wf_kyc_standard is a placeholder — replace it with the ID of your own workflow. When setting up a workflow in the Console, you choose its name; that name becomes the workflowId you pass here.
curl -X POST https://api.beltic.com/v1/workflows/execute \
  -H "X-Api-Key: $BELTIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflowId": "wf_kyc_standard",
    "options": {
      "input": {
        "subject_id": "user_jane_doe_001",
        "document_type": "passport",
        "document_front_url": "https://your-storage.com/passport_front.jpg",
        "jurisdiction": "US"
      }
    }
  }'

​
3. Handle the result

A 200 response means the workflow reached a terminal state — check result.status for completed or failed. A 202 means the workflow paused and is waiting on external input (e.g. a manual compliance review) before it can continue. That’s the core loop. From here, you can read the output directly, trigger downstream logic, or optionally use the Credentials API to package the result into a portable signed JWT for future use.
TypeScript SDK — coming soon. A first-class TypeScript SDK with generated types, automatic retries, and environment handling is in active development. The REST API is stable and production-ready today. Sign up for early access →

​
Core APIs

Workflow API

The execution plane. Configure verification pipelines once and trigger them with a single call. Built-in pause/resume for human-in-the-loop steps.

Credentials API

Package a verification result into a portable, cryptographically signed JWT. Present it at future checkpoints without re-running the workflow.

Document API

Extract structured data from documents with AI-powered processing and fraud detection.

Business API

Create and manage business entities. Look up registered companies and track their verification state across your platform.

Screening API

Run sanctions, PEP, and adverse media checks against individuals and entities. Integrates directly into workflows or as a standalone call.

Website Check API

Analyse a business’s web presence — category classification, risk signals, and policy compliance — in a single request.

​
Examples

Fintech Company Using Beltic

End-to-end walkthrough: user signup, sponsor bank queue, and transaction authorization — with exactly what your backend calls and what your user sees at every step.

Agent Authorization

Cryptographic proof that a verified human authorized an agentic transaction — with scoped permissions any endpoint can verify.

​
Authentication

All requests require an API key in the X-Api-Key header: 
X-Api-Key: sk_production_...
Use sk_staging_... keys in development. Keys are created in the Console and scoped per permission. See Authentication for rate limits, retry guidance, and idempotency.