Overview
Send the first six digits of any debit, credit, or prepaid card as the BIN parameter. The API resolves the number against payment card records and returns the card network, card type, issuing bank name, and issuing country. Paid plans add the issuer website, phone number, card category, and ISO country codes with coordinates.
Live Test BIN Grounding Data for AI Agents Source →
The tool
Once your client is connected to the VerveContext server, this appears in its tool list as BINGroundingDataforAIAgents. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.
{
"name": "BINGroundingDataforAIAgents",
"arguments": {
"bin": "448590"
}
}You do not name the tool yourself; the model picks it. Asking about 448590 in the terms this source covers is enough for it to reach for BINGroundingDataforAIAgents on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.
| Argument | Type | Description |
|---|---|---|
binRequired | string | The first six digits of the credit card number (BIN) length 6–8 |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"bin": "448590",
"brand": "VISA",
"type": "CREDIT",
"category": "PURCHASING",
"country": "United States",
"issuer": {
"name": "JPMORGAN CHASE BANK, N.A.",
"country": "United States",
"phone": "1-800-432-3117",
"website": "www.chase.com"
},
"location": {
"latitude": "37.0902",
"longitude": "-95.7129",
"alpha2": "US",
"alpha3": "USA"
}
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
bin | string | 448590 | The BIN number provided in the request |
brand | string | VISA | Card brand (VISA, Mastercard, American Express, etc.) |
type | string | CREDIT | Card type (CREDIT, DEBIT, PREPAID, etc.) |
categoryPremium | string | PURCHASING | Card category (PURCHASING, TRAVEL, etc.) |
country | string | United States | Country where card was issued |
issuer | object | {…} | The issuing bank: name, country, phone and website |
issuer.name | string | JPMORGAN CHASE BANK, N.A. | Full name of the issuing bank |
issuer.countryPremium | string | United States | Country where issuer is located |
issuer.phonePremium | string | 1-800-432-3117 | Contact phone number of the issuer |
issuer.websitePremium | string | www.chase.com | Official website URL of the issuer |
location | object | {…} | Issuing country coordinates and ISO codes |
location.latitudePremium | string | 37.0902 | Latitude coordinate of issuer location |
location.longitudePremium | string | -95.7129 | Longitude coordinate of issuer location |
location.alpha2Premium | string | US | Two-letter ISO country code of location |
location.alpha3Premium | string | USA | Three-letter ISO country code of location |
Why ground on it
A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.
Point an evaluation at brand: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.
Failure modes
Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This source is not part of VerveContext. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Checkout Brand Detection
- Display the matching Visa or Mastercard logo automatically when customers type the first six digits into your checkout form.
- Prepaid Card Blocking
- Reject or flag trial signups that supply prepaid cards before running an authorization charge.
- Debit Fee Optimization
- Route transactions through lower-cost debit payment rails whenever the lookup confirms an incoming debit card.
- Billing Country Mismatch
- Flag suspicious orders for manual review if the card issuing country does not match the customer billing address.
Other ways to use BIN Grounding Data for AI Agents
Set up BIN Grounding Data for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.
Related
More in Finance: