canonical: https://jentic.com/apis/usbank.com/usbank

# U.S. Bank Developer API

U.S. Bank open banking APIs for account information, payments, onboarding, and financial services. The API exposes 6 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get access token, list accounts. Covers 6 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Get access token
- List accounts
- Create instant payment
- Query and filter U.S. Bank Developer API records by parameters
- Monitor U.S. Bank Developer API operational status and events

## Use cases

### Finance and Accounting Operations

Use the U.S. Bank Developer API to perform finance operations programmatically. The API provides 6 endpoints covering core functionality including get access token, list accounts, get account details.

Example prompt: Call POST `/auth/token` to get access token

### Automated Accounts Management

Automate accounts operations by combining multiple U.S. Bank Developer API endpoints. Agents can list accounts and then get account details in a single workflow.

Example prompt: Call GET /accounts to list accounts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call U.S. Bank Developer API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'get access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Get access token |
| GET | `/accounts` | List accounts |
| GET | `/accounts/{account_id}` | Get account details |
| GET | `/accounts/{account_id}/transactions` | List account transactions |
| POST | `/payments/instant` | Create instant payment |
| POST | `/payments/ach` | Create ACH payment |

## Key resources

- **Accounts** — Operations for accounts
- **Auth** — Operations for auth
- **Payments** — Operations for payments

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 85 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/usbank.com/usbank/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the U.S. Bank Developer API by hand means running its OAuth2 token flow against `/auth/token`, refreshing the token, and threading it through account and payment calls yourself. Through Jentic you install once, import the U.S. Bank Developer API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** U.S. Bank puts the account id in the URL path (`/accounts/{account_id}/...`), so a rule can pin your agent to one account: it can read that account and its transactions and nothing else. You choose the operations it may call, so money-moving ones like instant or ACH payments are not included unless you add them.
- **Credential handling:** Your U.S. Bank OAuth2 credential 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 'obtain an access token' or 'list account transactions', and Jentic returns the matching U.S. Bank operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### What authentication does the U.S. Bank Developer API use?

The U.S. Bank Developer API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get access token with the U.S. Bank Developer API?

Yes. Use the POST `/auth/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the U.S. Bank Developer API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get access token'. Jentic returns the matching U.S. Bank Developer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the U.S. Bank Developer API have?

The U.S. Bank Developer API exposes 6 endpoints covering accounts, auth, payments operations.

### Can I limit what my agent is allowed to do with the U.S. Bank Developer API?

Yes. Jentic One is self-hosted, so your own rules decide which U.S. Bank operations and credentials the agent may use. Because the account id sits in the URL path (`/accounts/{account_id}/...`), you can pin the agent to a single account and let it read that account and its transactions and nothing else. You also choose the operations it may call, so money-moving endpoints like the instant and ACH payment calls stay off unless you add them.