BIN Lookup API

Name: BIN Lookup API API
Brand: BIN Lookup API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

Look up the issuer, scheme, and country of a payment card from its BIN (first 6-8 digits) and check the remaining query balance on the account.

Quickstart

Get started with BIN Lookup API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up bank issuer from card BIN"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BIN Lookup API API.

Resolve a 6-8 digit BIN into issuer bank name, card scheme (Visa, Mastercard, Amex), card type (debit, credit, prepaid), and issuing country

Verify whether a card BIN belongs to a prepaid product before authorising a recurring charge

Retrieve the remaining query balance on the Bintable account to forecast monthly usage

Augment fraud-screening rules with country-of-issue data pulled from the BIN response

GET STARTED

Start building with BIN Lookup API API

Explore with Jentic

View OpenAPI Document

Bintable's BIN Lookup API resolves the first 6 to 8 digits of a payment card (the Bank Identification Number) into the issuing bank, card scheme, card type, country, and prepaid flag. The service maintains a community-curated and third-party-augmented database of BIN entries that an integrator can call before authorising a transaction or routing a payment. The API exposes two endpoints: one to look up a BIN and one to retrieve the remaining quota balance on an account. Responses are JSON and the lookup latency is sub-second for cached entries.

Use Cases

Patterns agents use BIN Lookup API API for, with concrete tasks.

★ Pre-authorisation BIN screening

Merchants screen card prefixes before sending an authorisation to their PSP to block prepaid or specific-country cards on high-risk products. The /{bin} endpoint returns the issuer bank, scheme, type, and country in a single round trip, letting a checkout service add a synchronous decision step without changing its core payment flow. Latency on cached BINs is typically under 200 ms, so the additional check is invisible to the buyer.

Call GET /414720 and return bank name, scheme, type, and country to the checkout decision engine

Fraud-screening enrichment

Risk teams enrich each transaction record with the BIN-derived issuing country to detect mismatches against the buyer's IP geolocation or shipping address. Bintable's lookup returns a country ISO code that maps cleanly into common fraud-rule engines. The /balance endpoint lets the same team monitor remaining quota so a screening pipeline never silently fails on quota exhaustion.

For each new transaction, call /{bin} with the leading 6 digits, attach country and scheme to the fraud event, and alert when /balance drops below 1000

Agent integration via Jentic for card data lookup

An AI agent processing a user's checkout request can resolve a card BIN through Jentic by issuing the natural-language query 'look up bank issuer from card BIN'. Jentic returns the Bintable /{bin} operation with its input schema (a single path parameter) and response schema (issuer, scheme, type, country, prepaid flag). The agent never sees the raw API key — Jentic injects it from the encrypted vault.

Search Jentic for 'bank issuer from card bin', load the Bintable lookup schema, execute against BIN 414720, and return the issuer name

Key Endpoints

2 endpoints — bintable's bin lookup api resolves the first 6 to 8 digits of a payment card (the bank identification number) into the issuing bank, card scheme, card type, country, and prepaid flag.

METHOD

PATH

DESCRIPTION

GET

/{bin}

Look up issuer details for a 6-8 digit BIN

GET

/balance

Return the remaining BIN-lookup quota for the account

GET

/{bin}

Look up issuer details for a 6-8 digit BIN

GET

/balance

Return the remaining BIN-lookup quota for the account

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Bintable API keys are stored encrypted in the Jentic vault. Jentic injects the key as a query parameter at execution time, so agent prompts and logs never contain the raw secret.

Intent-based discovery

Agents search by intent (e.g. 'bank issuer from card BIN' or 'card country detection') and Jentic returns the Bintable /{bin} operation with its full input and response schema.

Time to first call

Direct Bintable integration: half a day to register, fetch a key, and wire up two endpoints. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

NeutrinoAPI

General-purpose data API including BIN lookup, IP geolocation, and email verification.

Choose NeutrinoAPI when the agent needs BIN lookup plus other enrichment (IP, email, phone) from a single vendor.

Alternative

APILayer

API marketplace that hosts several BIN lookup providers behind a unified key.

Choose APILayer when the agent already uses other APILayer services and wants to consolidate billing.

Complementary

RapidAPI

Marketplace listing competing BIN-lookup services with consolidated billing.

Use RapidAPI when the agent needs to compare BIN-lookup latency or coverage across providers.

FAQs

Specific to using BIN Lookup API API through Jentic.

What authentication does the Bintable BIN Lookup API use?

Bintable issues an API key that is appended as a query parameter on every request. Through Jentic the key is held encrypted in the vault and injected at call time, so the agent context never contains the raw secret.

Can I detect prepaid cards with the Bintable BIN Lookup API?

Yes. The /{bin} response includes a prepaid boolean field alongside the issuer bank name, card scheme, and country. Pass the leading 6 digits of the card number to the path and read response.data.prepaid.

What are the rate limits for the Bintable BIN Lookup API?

Bintable enforces a per-account daily quota rather than a per-second rate limit. Call GET /balance to read the remaining allowance for your key — the response returns a numeric balance you can poll on a schedule and alert on.

How do I look up a card issuer through Jentic?

Search Jentic for 'look up bank issuer from card BIN', load the Bintable /{bin} operation schema, then execute with the 6-digit BIN as the path parameter. The standard pip install jentic flow plus an asyncio search-load-execute call returns the issuer in one round trip.

Is the Bintable BIN Lookup API free?

Bintable offers a free tier with a daily quota plus paid plans for higher volumes. Use the /balance endpoint to monitor remaining queries on the active key — when balance is exhausted the /{bin} endpoint returns an error.

How fresh is the BIN database the API queries?

Bintable maintains the database from community submissions and third-party feeds. Newly issued BINs typically appear within days. For mission-critical fraud rules, treat unknown-BIN responses as a soft signal rather than a hard reject.