canonical: https://jentic.com/apis/cardbincheck.com/cardbincheck # CardBinCheck BIN Lookup API The CardBinCheck API performs a BIN or IIN lookup: give it the first six to eight digits of a card number and it returns the card's scheme, funding type, issuer, and country. A single lookup handles one BIN, and a batch call resolves up to 100 BINs in one request. Keyless use is allowed under a per-IP daily limit, and a free IPNOVA API key raises that limit and works across every IPNOVA API. ## For AI agents Look up the scheme, funding type, issuer, and country for a card BIN, one at a time or up to 100 in a batch. Works keyless under a per-IP daily limit or with an optional free API key. ## Scope Does not process payments, store card numbers, or verify a cardholder's identity. Use for BIN and IIN metadata lookups only. ## Capabilities - Look up a single BIN or IIN from the first six to eight digits of a card number - Return a card's scheme, funding type, issuer, and country - Resolve up to 100 BINs in a single batch request - Check a card prefix before starting a payment or fraud-review flow ## Use cases ### Agent-Side Card Routing An AI agent checks a card BIN through Jentic before it routes a payment or applies a rule, pulling the scheme, funding type, and issuing country for the prefix. The lookup works keyless under a per-IP daily limit, or with a stored IPNOVA key for a higher limit, and the agent calls it by intent without wiring the endpoint by hand. Because it only reads BIN metadata, it never touches a full card number or a payment. Example prompt: Look up the BIN for a card prefix and branch the workflow on whether the funding type is debit or credit. ### Checkout Risk and Routing A checkout flow identifies a card's scheme, funding type, and country from its BIN to pick a processor, apply surcharges, or flag high-risk geographies. CardBinCheck returns issuer and country for the first six to eight digits, so the decision happens before authorization. A batch endpoint resolves many BINs at once for bulk reconciliation. Example prompt: Resolve a list of 100 BINs in one batch call and group the cards by issuing country. ### Bulk BIN Enrichment A finance team enriches a stored list of card prefixes with issuer, scheme, and funding type for reporting or reconciliation. The batch lookup accepts up to 100 BINs per call, and keyless access covers light use while a free key lifts the daily limit. The returned fields describe only the card product, not any individual cardholder. Example prompt: Enrich a stored list of card BINs with scheme and issuer, calling the batch endpoint in groups of up to 100. ## Key resources - **BIN lookup** — Look up one BIN or IIN and return its scheme, funding type, issuer, and country - **Batch lookup** — Resolve up to 100 BINs in a single request ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 61 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 94 / 100 - Developer Experience & Jentic Compatibility: 71 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/cardbincheck.com/cardbincheck/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the CardBinCheck API by hand means deciding whether to send the optional IPNOVA key in the `X-Api-Key` header and handling the per-IP daily limit when you go keyless. Through Jentic you install once, import CardBinCheck from the API Directory, store the key once if you use one, and your agent calls it. - **Permission scoping:** The API has only two read operations, so a rule bounds your agent to the single-BIN lookup, the batch lookup, or both. There is nothing destructive to allow, and you decide whether batch access is included. - **Credential handling:** If you use an IPNOVA key, it is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'look up a card BIN', and Jentic returns the matching CardBinCheck operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **NeutrinoAPI** — A toolkit of data APIs that includes BIN lookup alongside other utilities. - **apilayer** — A marketplace of hosted data APIs with BIN and bank-data endpoints. - **Checkout.com** — A payment platform that authorizes and captures the cards you identify. ## FAQ ### What authentication does the CardBinCheck API use? The CardBinCheck API accepts an optional IPNOVA API key in the `X-Api-Key` header, per its OpenAPI spec. Keyless calls work under a per-IP daily limit, and the free key raises that limit and works across every IPNOVA API. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time when you provide one. ### Can I look up a card's issuer and country by BIN? Yes. Give the API the first six to eight digits of a card number and it returns the card's scheme, funding type, issuer, and country. A batch call resolves up to 100 BINs in one request for bulk work. ### What are the rate limits for the CardBinCheck API? Keyless use is capped per IP per day, and a free IPNOVA API key raises the limit, but the OpenAPI spec does not state the exact numbers. Check the vendor's documentation at https://api.ipnova.com for current limits. ### Can I limit what my agent is allowed to do with the CardBinCheck API? Yes. The API exposes two read lookups, so a rule limits the agent to the single-BIN lookup, the batch lookup, or both. Nothing it can call writes data or moves money, and every call it makes is logged. ### Is there a CardBinCheck MCP server? You don't need an MCP server to give your agent the CardBinCheck API. Jentic connects it directly from the API Directory: import it, store an optional key once, and your agent calls the single and batch BIN lookups. You skip loading another server's tool definitions into the agent's context. ### How do I look up a card BIN through Jentic? Add the CardBinCheck API from the Jentic API Directory and store an IPNOVA key once if you use one. Your agent then searches by intent such as 'look up a card BIN' and Jentic returns the matching operation with its input schema, so it can resolve the prefix and read the scheme and issuer. To run it on your own infrastructure, install Jentic One from its GitHub repo.