BizVerify

BizVerify in Anthropic.

Tool definitions live at api.bizverify.co/tools/anthropic.json. Drop into anthropic.messages.create unchanged.

Tool JSON at api.bizverify.co/tools/anthropic.json
Get a free API keyRead the Anthropic guide →

Install.

  1. 01

    Fetch the hosted tool definitions

    BizVerify maintains the canonical Anthropic tool schema at a public JSON endpoint. Fetch it once at startup and pass the array directly into anthropic.messages.create.

    const tools = await fetch("https://api.bizverify.co/tools/anthropic.json").then(r => r.json());
  2. 02

    Route tool_use blocks back to the API

    Claude emits a tool_use content block. Route it on block.name to the matching BizVerify SDK call.

  3. 03

    Store the API key as a header

    Authorize every BizVerify request with the X-API-Key header. The same key works across the SDK, REST API, MCP server, and the n8n node.

What Anthropic exposes.

Nine operations. The same nine across every integration on this site.

  • verify_business

    Quick or deep verification of an entity in one jurisdiction.

  • search_entities

    Find entities matching a name in a jurisdiction.

  • check_job_status

    Poll a long-running verification job by id.

  • get_entity

    Fetch a previously verified entity from cache.

  • get_entity_history

    Return the verification history for an entity.

  • get_account

    Read account info and credit balance.

  • get_config

    Read public service config and supported jurisdictions.

  • list_jurisdictions

    List active jurisdictions and their status.

  • purchase_credits

    Buy additional credits from your agent loop.

One real example.

Pass the hosted tool definitions into anthropic.messages.create

import Anthropic from "@anthropic-ai/sdk";
import { BizVerify } from "@bizverify/sdk";

const client = new Anthropic();
const biz = new BizVerify({ apiKey: process.env.BIZVERIFY_API_KEY! });

const tools = await fetch("https://api.bizverify.co/tools/anthropic.json")
  .then(r => r.json());

const message = await client.messages.create({
  model: "claude-sonnet-4-6",
  max_tokens: 1024,
  tools,
  messages: [{ role: "user", content: "Is Acme Corp registered in Delaware?" }],
});

const block = message.content.find(b => b.type === "tool_use");
if (block?.name === "verify_business") {
  const result = await biz.verification.verify(block.input);
  // feed result back as a tool_result content block in the next turn
}

Why BizVerify for Anthropic.

  • Schema lives in our infra, not yours

    Tool definitions are fetched, not vendored. When BizVerify adds or refines a parameter, your agent picks it up on next deploy.

  • Block names map to SDK methods

    verify_business in the tool_use block is biz.verification.verify in the SDK. Routing tool_use blocks is a switch on block.name.

  • Same key everywhere

    One BIZVERIFY_API_KEY environment variable works across the SDK, the REST API, MCP, and the n8n node. No per-integration credentials.

What verification is, and isn't.

We confirm what the official registry currently says about an entity. We don't claim more than that.

BizVerify does

  • Confirms the entity is registered with the official government registry
  • Returns the current registry status (active, dissolved, suspended, etc.)
  • Returns canonical entity name, type, and jurisdiction id

BizVerify does not

  • Verify solvency, credit, or financial standing
  • Verify beneficial ownership or directors/officers (quick check)
  • Verify that the model's user is authorized by the entity
  • Flag sanctions or PEP exposure

See also.

Start verifying inside Anthropic.

Fifty free credits on signup. No card. Same key across every integration on this site.

Get a free API keyOpen the Anthropic guide →