# Agent Budget Guard – Classify Invoice

> Agent Budget Guard – Classify Invoice is a paid API for AI agents from agent-budget-guard.onrender.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Classifies a Japanese business transaction to determine invoice eligibility and tax treatment under Japan's qualified invoice (Tekikaku Seikyusho) system

## Facts

- Endpoint: POST https://agent-budget-guard.onrender.com/api/classify-invoice
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-budget-guard-classify-invoice-dabfbaaf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tMfiFqg-jBZ1QRTKYDAYe

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 agent-budget-guard-classify-invoice-dabfbaaf -d '<json body>'
```

Example prompt: Classify this invoice: the transaction date is 2024-11-15, the seller is invoice registered, the total amount including tax is 110,000 JPY, and our company's annual taxable sales are 50,000,000 JPY — tell me if this qualifies under Japan's invoice system.

## When to prefer this

Use this endpoint when you need to programmatically classify Japanese business invoices for consumption tax compliance, particularly for autonomous agents handling JPY or JPYC-denominated transactions that must generate audit-ready records. Ideal for workflows involving Japanese B2B procurement, expense reporting, or tax credit validation where the qualified invoice system (Tekikaku Seikyusho) applies.

## Known failure modes

- Missing required fields (transaction_date, buyer_taxable_sales_jpy, seller_invoice_registered, transaction_amount_tax_included_jpy) result in validation error
- Invalid date format (not YYYY-MM-DD) causes parsing failure
- Non-numeric JPY amount strings may cause computation errors
- Payment failure via x402 (insufficient USDC balance) blocks the request
- Seller registration status value not recognized causes classification to fail

## How this service works

Pay-per-request governance APIs for AI agents using x402. Check budgets, log payments, classify invoices, and generate audit-ready spending records. Built for autonomous agents, USDC/Base payments, and JPY/JPYC reporting workflows.

## Output

Returns a classification of the transaction's status under Japan's qualified invoice (Tekikaku Seikyusho) system, indicating tax eligibility, whether the buyer can claim an input tax credit, and the applicable consumption tax treatment based on seller registration status and transaction parameters.

## Example request

```json
{
 "transaction_date": "2024-01-15",
 "buyer_taxable_sales_jpy": "50000000",
 "seller_invoice_registered": "true",
 "transaction_amount_tax_included_jpy": "1100000"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "transaction_date": {
   "type": "string",
   "description": "Transaction date YYYY-MM-DD"
  },
  "buyer_taxable_sales_jpy": {
   "type": "string",
   "description": "Buyer annual taxable sales in JPY"
  },
  "seller_invoice_registered": {
   "type": "string",
   "description": "Whether seller is invoice registered"
  },
  "transaction_amount_tax_included_jpy": {
   "type": "string",
   "description": "Transaction amount including tax in JPY"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-budget-guard-classify-invoice-dabfbaaf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-budget-guard.onrender.com](https://www.zero.xyz/host/agent-budget-guard.onrender.com/llms.txt)