# Agentshelf IBAN Regex Extractor

> Agentshelf IBAN Regex Extractor is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-29).

Extracts up to 20 IBAN-shaped tokens from a given text string using regex matching, billed per call.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/regex-iban?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshelf-iban-regex-extractor-cf413723
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1ci6AgJKNCpf8YHQoouqU

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 agentshelf-iban-regex-extractor-cf413723 -d '<json body>'
```

Example prompt: Can you pull out all the IBAN numbers from this text for me? Here's the content: 'Please transfer funds to DE89370400440532013000 or alternatively to GB29NWBK60161331926819 before the deadline.'

## When to prefer this

Use this endpoint when you need fast, local regex-based IBAN token extraction from text without any network fetching or validation logic. It is best suited for scanning raw text blobs, emails, contracts, or tickets for IBAN-shaped strings. Prefer the free sandbox POST /v1/sandbox/regex-iban endpoint for testing or when cost matters. Do not use this for IBAN checksum validation — use the sibling mod-97 validator endpoint for that. This endpoint does not fetch URLs or parse HTML; it operates purely on submitted text.

## Known failure modes

- Empty match list returned even when IBANs are present if they are malformed or non-standard
- Only up to 20 matches returned; additional IBANs beyond the cap are silently ignored
- Empty input or whitespace-only text returns an empty match list but is still billed
- Text exceeding 100,000 characters will be rejected with a validation error
- Network or payment processing errors may prevent the call from completing

## How this service works

Call when an agent needs IBAN-shaped tokens extracted from text, capped at 20 matches. An empty match list is billed. No network. Exact $0.007 USDC. Prefer unpaid POST /v1/sandbox/regex-iban first.

## Output

A list of up to 20 IBAN-shaped string tokens found in the submitted text via regex pattern matching. If no IBANs are found, an empty list is returned — the call is still billed regardless.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "examples": [
    "GB82WEST12345698765432"
   ],
   "maxLength": 100000,
   "minLength": 1,
   "description": "Input for this SKU. The route description says whether it is plain text, a URL, base64 bytes, or an already-encoded token."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshelf-iban-regex-extractor-cf413723/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)