Israel Invoice Payment Gate and Counterparty Intelligence

One agent-native gate to check an Israeli supplier invoice before payment, with public-registry counterparty evidence.

Public source: https://github.com/itzikhr18/israel-counterparty-intelligence

Bring your own trusted wallet: the free invoice result can prepare a private, validated request for an existing x402 client, with a free supplier match and a 0.25 USDC proposed cap. No seller wallet package is required. Downloading is not payment approval; the buyer's wallet must enforce the live terms. Independent-wallet guide.

Start with the free invoice check, download the validated invoice-request.json, and continue with the same invoice:

npx --yes https://israel-counterparty-intelligence.vercel.app/israel-company-verify-buyer-0.4.0.tgz --invoice-file invoice-request.json

Public agent metadata is available at /.well-known/x402, /llms.txt, and /README.md in the production deployment. The Mainnet and Testnet payment resources use the same business logic but remain separate payment routes so Test USDC can never unlock the Mainnet resource.

The same verification engine is also exposed as a stateless Remote Streamable HTTP MCP server:

• POST /mcp - Base Mainnet, including a 0.25 USDC Israeli invoice payment gate plus company changes, verification, and vendor-risk tools.
• POST /mcp/testnet - Base Sepolia, 0.05 Test USDC per successful verify_company call.
• POST /mcp/pilot - invitation-only partner evaluation with a time-limited bearer token.
• Company and payment-risk previews, preview_agent_payment_trust, describe_service, and get_schema are free on both MCP endpoints.

This repository is a deliberately small MVP for External Paid Call #1. It resolves an Israeli registered company, adds its public government-contract/support footprint, builds field-level evidence, and returns a transparent heuristic risk signal. It is not a legal, credit, sanctions, or investment service.

Current scope

• POST /v1/verify - official company resolution and evidence.
• POST /v1/verify/mainnet - the same verification result, paid with real USDC on Base Mainnet.
• POST /v1/pilot/verify - invitation-only partner evaluation; never a public free route.
• POST /v1/government-footprint - public contracts and supports by exact company number.
• POST /v1/counterparty-risk - combined result and deterministic reason-coded score.
• POST /v1/payment-risk/mainnet - Mainnet pre-payment vendor triage with a PROCEED, REVIEW, or BLOCK result.
• POST /v1/invoice-gate/preview - free invoice arithmetic and allocation-applicability preview using date, amount, VAT component, and buyer-attested conditions; never authorization to pay.
• POST /v1/invoice-gate/mainnet - 0.25 USDC registry-backed Israeli invoice gate returning PAY, HOLD, or BLOCK.
• POST /v1/company-changes/mainnet - recent official company filing and status-change events for an exact company number, newest first, with source evidence.
• POST /v1/agent-payment-trust - free dry-run x402 pre-sign firewall with ALLOW, REVIEW, or DENY; it never signs or submits a payment.
• GET /health - health check.
• GET /openapi.json - machine-readable contract.
• x402 v2 fixed-price protection and Bazaar metadata when X402_ENABLED=true.
• Remote Streamable HTTP MCP with paid verify_company plus free preview_company, preview_agent_payment_trust, describe_service, and get_schema.

Allocation applicability uses a strictly-greater-than amount threshold and also depends on a VAT component, an authorized-dealer buyer, and a buyer request; missing buyer context fails safely to HOLD. Official Tax Authority allocation verification requires an authorized dealer/representative connection. Buyer-supplied verification results are labeled BUYER_ATTESTED and are not independently authenticated. Not included: dashboards, accounts, subscriptions, PDF reports, broad scraping, bank-account ownership verification, document forensics, UBO/PEP/sanctions certification, adverse-media screening, creditworthiness, TASE enrichment, or a custom ML model.

Verified Payee Firewall MVP

preview_agent_payment_trust evaluates exact x402 terms before a buyer wallet signs. It resolves the claimed Israeli company, fetches /.well-known/agent-payee.json from the service origin with SSRF and redirect protections, validates the manifest and EVM signature, checks the declared payment destination, verifies the payment resource origin and buyer mandate, and creates a stable SHA-256 fingerprint of the payment contract.

ALLOW is fail-closed: it requires an active resolved company, a valid domain-fetched manifest, an authorized payment destination, a matching resource origin, and a complete buyer mandate. REVIEW and DENY must not be signed automatically. Level 1 and Level 2 assurance do not prove legal ownership of the recipient wallet. The manifest specification is published at /agent-payee-manifest-v0.1.md and its JSON Schema at /.well-known/agent-payee-schema.json.

Production status: MAINNET LIVE - AWAITING FIRST EXTERNAL PAID CALL. No internal Mainnet payment is required for launch. The first genuine external Base Mainnet USDC payment is also the first production end-to-end settlement and External Paid Call #1.

Public sources

The company adapters use the Ministry of Justice Companies Registrar open CKAN company dataset and the Corporations Authority daily changes dataset on data.gov.il. The changes source covers up to approximately one year; an empty result does not prove that no earlier change occurred. Official request types are returned as facts and mapped to deterministic navigation categories, not risk conclusions. The government-footprint adapter uses the public BudgetKey table API. Source URLs, retrieval time, source record identifiers, and confidence are returned in evidence.

The service returns null and missing_data when data is unavailable. It does not convert a government contract into a trust endorsement and does not add risk points merely because a source is missing.

Local setup

Requirements: Node.js 20 or newer.

npm install
cp .env.example .env.local
npm run dev

Run all checks:

npm run check

Example

curl -X POST http://localhost:3000/v1/verify \
  -H 'content-type: application/json' \
  -d '{"company_number":"514744887","language":"en"}'

Name lookup is also supported:

{
  "company_name": "MONDAY.COM",
  "city": "Tel Aviv",
  "language": "en"
}

When several candidates are plausible, the API returns 409 AMBIGUOUS_ENTITY and candidates. It never silently selects one. An invalid number returns 400; no reliable entity returns 422 for the two enrichment endpoints.

x402 configuration

The implementation uses the official x402 v2 packages and Next.js withX402, so settlement occurs only after a successful response. The default test setup is Base Sepolia through the public x402 test facilitator.

Required to enable payment:

X402_ENABLED=true
X402_PAY_TO=0xYourReceivingWallet
X402_NETWORK=eip155:84532
X402_ASSET=0x036CbD53842c5426634e7929541eC2318f3dCF7e
X402_FACILITATOR_URL=https://facilitator.payai.network
PUBLIC_BASE_URL=https://your-public-host.example

Prices are centralized in environment variables:

X402_VERIFY_PRICE=$0.10
X402_GOVERNMENT_PRICE=$0.35
X402_RISK_PRICE=$0.50

The independent Mainnet resource uses:

X402_MAINNET_ENABLED=true
X402_MAINNET_PAY_TO=0xYourReceivingWallet
X402_MAINNET_NETWORK=eip155:8453
X402_MAINNET_ASSET=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
X402_MAINNET_FACILITATOR_URL=https://facilitator.payai.network
X402_MAINNET_FACILITATOR_PROVIDER=auto
CDP_API_KEY_ID=
CDP_API_KEY_SECRET=
X402_MAINNET_VERIFY_PRICE=$0.05
X402_MAINNET_PAYMENT_RISK_PRICE=$0.10
X402_MAINNET_INVOICE_GATE_PRICE=$0.25
X402_MAINNET_COMPANY_CHANGES_PRICE=$0.01
X402_MCP_TESTNET_VERIFY_PRICE=$0.05
X402_MCP_MAINNET_VERIFY_PRICE=$0.05
X402_MCP_TESTNET_PAYMENT_RISK_PRICE=$0.10
X402_MCP_MAINNET_PAYMENT_RISK_PRICE=$0.10
X402_MCP_TESTNET_INVOICE_GATE_PRICE=$0.25
X402_MCP_MAINNET_INVOICE_GATE_PRICE=$0.25
X402_MCP_TESTNET_COMPANY_CHANGES_PRICE=$0.01
X402_MCP_MAINNET_COMPANY_CHANGES_PRICE=$0.01
MAINNET_INTERNAL_TEST_PAYER=0xYourIsolatedMainnetTestWallet

Without a payment signature, a protected endpoint returns 402 with PAYMENT-REQUIRED. The challenge includes Bazaar input/output metadata. A compatible paid client must echo that extension in its payment payload. Catalog inclusion happens only after a facilitator processes a conforming paid payload and is ultimately controlled by that facilitator.

X402_MAINNET_FACILITATOR_PROVIDER=auto preserves the configured URL until both CDP credentials are present. When they are added, Mainnet verification and settlement automatically switch to the authenticated Coinbase CDP facilitator. The secret never appears in challenges, logs, or health responses. Run npm run bazaar:check to validate all live paid endpoints against Coinbase Bazaar; the same read-only check runs daily in GitHub Actions.

The Base Sepolia and Base Mainnet network identifiers and USDC assets are validated as distinct configuration values. Price, asset, network, facilitator and payTo are server-owned and cannot be overridden by request input.

MCP client setup

Production MCP URL:

https://israel-counterparty-intelligence.vercel.app/mcp