BankIntel

BANKINTEL FOR AUTONOMOUS CLIENTS

Give your agents
financial context.

Discover the service, retrieve structured bank intelligence, and carry the evidence into the answer.

{ }llms.txtPLAIN TEXT

BankIntel / service discovery

Bank identity → FDIC CERT
Financial evidence → JSON
Request access → x402 V2
One intelligence engine.
Ready for programmatic retrieval.

01 / THE INTEGRATION

Retrieve evidence at question time.

A banking assistant can call BankIntel when a conversation needs public institution financials, historical movement, peer context, or market intelligence. The client chooses the resource, makes the request, and provides the returned evidence to its model.

This is API tool use. It does not require retraining a model on each new quarterly filing. Your platform continues to manage its own user permissions, conversation, and institution-specific information.

Two integration paths.

Enterprise access is agreed with BankIntel. Compatible autonomous clients can use public x402 resources with per-request payment. A native connector to a specific AI platform is not implied.

02 / DISCOVER

Start with the service contract.

Service discoveryShell
curl 'https://bankintel.onrender.com/llms.txt'

The plain-text manifest remains on the API host for machine discovery. This page is its human-readable companion.

03 / RETRIEVE

Choose the evidence for the question.

  1. 01

    Resolve the institution.

    Search by bank name and confirm the correct legal institution. Use the returned FDIC cert for bank-specific requests.

  2. 02

    Request the relevant resources.

    Use snapshots for current financial context, trends for historical movement, and peers for same-quarter comparisons. Use geography for annual deposit-market context.

  3. 03

    Return evidence to the conversation.

    Supply the figures with their reporting periods, source context, units, and methodology. The model can then explain the results and answer follow-up questions.

Example question

“How has this bank’s liquidity changed, and how does it compare with similarly sized banks?” A client would typically combine liquidity, historical financials, and peers, while keeping the bank and cohort reporting periods explicit.

04 / X402 ACCESS

A request with a payment handshake.

Paid public endpoints use x402 V2 and the exact scheme with USDC. An initial unpaid request returns HTTP 402 and payment-requirement metadata. A compatible x402 client completes the protocol within its authorized spending policy.

Inspect a paid resourceShell
curl -i 'https://bankintel.onrender.com/v1/banks/18199/snapshot'

Read the live requirement.

Use the endpoint’s payment metadata for the network, asset, amount, and recipient. Default prices in documentation are not a substitute for that live requirement.

Use the configured network.

The live catalog identifies the network. Base mainnet is eip155:8453; Base Sepolia is eip155:84532. Do not assume which is active from a sample.

Count requests, not conversations.

One user question can require several resources. Define the client’s request and spending limits accordingly.

05 / TOOL DEFINITIONS

Give the model a focused tool.

Your application can wrap a BankIntel endpoint in its own tool-calling interface. The definition below is an illustrative function schema; adapt it to the platform you use.

Illustrative tool definitionJSON
{
  "name": "get_bank_snapshot",
  "description": "Retrieve public bank financial context. Preserve reporting dates, units, sources, and missing values.",
  "parameters": {
    "type": "object",
    "properties": {
      "cert": {
        "type": "integer",
        "minimum": 1,
        "description": "FDIC certificate from bank search"
      }
    },
    "required": ["cert"],
    "additionalProperties": false
  }
}

The application maps the tool call to GET /v1/banks/{cert}/snapshot and handles authentication or x402 payment outside the model’s arguments.

06 / ANSWER WITH CONTEXT

Make the evidence survive the handoff.

Suggested evidence instructionsPlain text
When using BankIntel evidence:
- Identify the bank and FDIC certificate.
- State the financial reporting period.
- Preserve source and calculation context.
- Interpret each field's dollar or ratio units correctly.
- Treat null as unavailable, never zero.
- Keep bank and peer reporting dates distinct.
- Describe quarterly figures as reported financials.
- Explain unavailable data and request failures.
- Do not infer supervisory ratings from descriptive metrics.

BankIntel provides factual public regulatory-data intelligence. Your platform controls how that evidence is presented, reviewed, and combined with authorized internal information.

BUILD SOMETHING USEFUL

Let’s find the right fit.

Tell us about your platform, expected usage, and the questions you want to answer.

LET’S TALK BANKINTEL

Tell us what you’re building.

Tell us about your use case. Continue in your email app to review and send your message to hello@getbankintel.com.