# AgentBIT Counterparty Verify

> AgentBIT Counterparty Verify is a paid API for AI agents from agentbit.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-11).

Screens a person, company, or EVM wallet address for sanctions exposure, domain-level technical risk, and GLEIF legal entity verification in a single call

## Facts

- Endpoint: POST https://agentbit.app/v1/kits/counterparty-verify?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentbit-counterparty-verify-c812561f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mc9Ty_MkdqtkAVMezyiIV

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentbit-counterparty-verify-c812561f -d '<json body>'
```

Example prompt: Before I wire payment to Nexus Trading Ltd, can you screen them for sanctions exposure, verify their legal entity via GLEIF, and also check their domain nexustrading.com for any technical risk flags?

## When to prefer this

Choose this endpoint when an AI agent needs to perform multi-dimensional counterparty due diligence in a single call — combining sanctions screening, legal entity verification, domain risk, and on-chain wallet risk — without requiring API key setup. Prefer over single-purpose compliance APIs when you need cross-checking across multiple risk dimensions for one counterparty, or when operating in a pay-per-call x402 context with no prior registration.

## Known failure modes

- Name not found on any sanctions list — returns clean result, not an error
- GLEIF lookup may return no match for unregistered or misspelled company names
- EVM address must be valid 0x + 40 hex format or will return validation error
- Domain may return limited signals if it is newly registered or obscure
- Ambiguous person names may produce multiple or zero sanctions matches
- API may return empty example response if the service is unavailable or the query is malformed

## How this service works

One AML/KYC-style verdict for a counterparty from a single call: wallet sanctions + on-chain risk, name sanctions screening, GLEIF company identity and technical counterparty risk, merged into clear | review | blocked with an itemized findings list. $0.02.

## Output

A JSON object containing results from one or more of: sanctions list screening hits for the named person or entity, domain-level technical risk indicators (e.g. malicious activity, reputation signals), GLEIF legal entity registration data for the company name, and wallet address risk flags for the EVM address — depending on which input fields were provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "Person or entity name to screen against sanctions lists"
  },
  "domain": {
   "type": "string",
   "description": "Domain to run technical counterparty risk on"
  },
  "address": {
   "type": "string",
   "description": "EVM wallet address to screen (0x + 40 hex)"
  },
  "company_name": {
   "type": "string",
   "description": "Legal company name to verify via GLEIF"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentbit-counterparty-verify-c812561f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentbit.app](https://www.zero.xyz/host/agentbit.app/llms.txt)