---
name: api.invoket.com
description: api.invoket.com provides three data validation and enrichment utilities: French company lookup via the INSEE Sirene register, IBAN validation with sanctions screening against OFAC/EU/UN/FATF lists, and phone number validation using Google's libphonenumber metadata. All three skills operate against offline or snapshot datasets rather than live network or registry feeds.
host: api.invoket.com
---

# api.invoket.com

InvokeT is a lightweight compliance and data-quality host targeting onboarding, invoicing, and payment workflows that require structured validation of counterparty data. It serves agents that need to verify French legal entities by SIREN/SIRET, confirm bank account legitimacy and sanctions status by IBAN, or normalize and validate phone numbers before storage or messaging. It does not cover entity name screening, real-time transaction monitoring, or non-French company registries.

## When to use this host

Use this host when an agent is onboarding or paying a French legal entity and needs structured validation of SIREN/SIRET identity, IBAN sanctions status, or phone number format. It is the right choice for AML/KYB pre-payment checks on bank accounts and for normalizing contact data. Do not use it for: screening individuals or entities by name (use a dedicated PEP/sanctions name-search API); monitoring live transactions; looking up non-French companies (use a global company registry API such as OpenCorporates); real-time carrier or number reachability checks (use a live HLR lookup service); or obtaining live registry data, as all three skills rely on periodic snapshots rather than real-time sources.

## Capabilities

### Counterparty Identity Verification

Resolves and validates the legal identity of a French company using the official INSEE Sirene register, returning structured legal and operational metadata needed for onboarding or invoicing.

- **`resolve-french-company-by-siren`** — Looks up a French legal entity by SIREN or SIRET in the official INSEE Sirene register and returns legal name, status, legal form, NAF activity code, workforce band, creation date, and head-office address.

### Payment Account Compliance

Validates an IBAN's format and screens the associated bank and jurisdiction against major international sanctions and AML risk lists, confirming whether a bank account is safe to pay.

- **`screen-iban-sanctions`** — Validates an IBAN and screens the associated bank and jurisdiction against OFAC, EU, UN, and FATF sanctions lists, returning bank details, BIC, and risk status.

### Contact Data Normalization

Validates and normalizes phone numbers to E.164 format using libphonenumber metadata, resolving country, line type, and canonical formats for storage or messaging use.

- **`validate-phone-number`** — Validates a phone number against Google's libphonenumber metadata and returns E.164 format, national format, country, line type, and validity flag.

## Workflows

### French Supplier Onboarding Check

*Use when an agent needs to onboard a new French supplier and must verify their legal entity, validate their bank account for payment, and normalize their contact phone number before creating a vendor record.*

1. **`resolve-french-company-by-siren`** — Verify the supplier's legal name, status, legal form, and registered address using their SIREN or SIRET number.
2. **`screen-iban-sanctions`** — Validate the supplier's provided IBAN and confirm their bank and country are not sanctioned or high-risk before enabling payments.
3. **`validate-phone-number`** — Normalize and validate the supplier's contact phone number to E.164 format and confirm line type before storing in the vendor record.

## Skill reference

### `resolve-french-company-by-siren`

**French Company Resolve (SIREN/SIRET)** — Looks up a French legal entity by SIREN or SIRET in the official INSEE Sirene register and returns legal name, status, legal form, NAF activity code, workforce band, creation date, and head-office address.

*Use when:* Use when an agent needs to verify or enrich a French company record before invoicing, payment, or onboarding — given a 9-digit SIREN or 14-digit SIRET number.

*Not for:* Do not use for non-French companies or for real-time registry data; the source is a monthly INSEE snapshot, not a live feed. Do not use when only a company name is available — a SIREN or SIRET is required.

**Inputs:**

- `siren` (string, required) — 9-digit SIREN of the legal unit. Provide exactly one of 'siren' or 'siret'. Returns 400 INVALID_INPUT for malformed input, 400 INVALID_CHECKSUM for Luhn failure, 404 (unbilled) if well-formed but absent from the register.

**Returns:** Returns a data object with SIREN, legal name, acronym, active status, legal form, NAF activity code, workforce bracket, creation date, headquarters SIRET and address, plus provenance metadata from the insee-sirene monthly snapshot.

**Example:** `GET https://api.invoket.com/company/resolve?siren=552081317`

---

### `screen-iban-sanctions`

**IBAN Screening API** — Validates an IBAN and screens the associated bank and jurisdiction against OFAC, EU, UN, and FATF sanctions lists, returning bank details, BIC, and risk status.

*Use when:* Use when an agent needs to verify a counterparty bank account before onboarding or making a payment — specifically to check IBAN validity, resolve bank name and BIC, and confirm the bank and country are not sanctioned or high-risk under AML/KYB compliance requirements.

*Not for:* Do not use for real-time transaction monitoring or individual person/entity name screening; use a dedicated PEP/sanctions name-search API for those cases.

**Inputs:**

- `iban` (string, required) — The IBAN to validate and screen. Must be a well-formed IBAN string.

**Returns:** Returns a data object with IBAN validity, resolved bank name and BIC, sanctions screening verdict (risk, bank_sanctioned, jurisdiction level, hits), coverage level, and a provenance block indicating the sanctions source and data freshness.

**Example:** `GET https://api.invoket.com/iban/screen?iban=DE89370400440532013000`

---

### `validate-phone-number`

**InvokeT Phone Validator** — Validates a phone number against Google's libphonenumber metadata and returns E.164 format, national format, country, line type, and validity flag.

*Use when:* Use when an agent needs to verify and normalize a phone number before storing, displaying, or messaging it — particularly to confirm validity, resolve E.164 format, or determine line type (mobile, fixed, etc.).

*Not for:* Do not use for real-time carrier lookups or live number reachability checks; this is an offline metadata validation based on a libphonenumber snapshot, not a live network query.

**Inputs:**

- `number` (string, required) — The phone number to validate. Can be in E.164 or local format.
- `country` (string, required) — ISO 3166-1 alpha-2 country code used as the default region for parsing the number.

**Returns:** Returns a data object with valid=true, E.164 format, national format, country code, and number_type=mobile, plus provenance metadata identifying the libphonenumber snapshot used.

**Example:** `GET https://api.invoket.com/phone/validate?number=%2B33612345678&country=FR`

---
