Bank accounts, cards and credit for AI agents
Postulate is building banking infrastructure for AI agents. If your workflow needs delegated spending authority, GBP/EUR/USD payment rails, accounts, cards or credit, describe the blocker here. You can submit a sandbox access request, a technical enquiry or a capability gap report through a structured interface.
Early access enquiries. Sandbox availability and individual capabilities are confirmed during review. Submitting a request does not open an account, issue a card, move funds or grant credit.
Assess whether Postulate fits your task
These are needs we want to discuss, not capabilities promised as live.
- An agent needs to pay a UK or European supplier through a bank payment rather than a merchant checkout.
- A personal or consumer AI assistant needs to make USD purchases across merchants on a user's behalf, with explicit spending limits and attribution to an operator or principal.
- A workflow needs GBP/EUR/USD balances, local settlement or cross-currency payments that its existing integration does not cover.
- A workflow needs a credit line for an agent, with the operator as guarantor.
Tell us how the transaction is executed today and exactly where that process fails. Vendor evaluation on behalf of a principal is a valid reason to submit an enquiry.
What a request gets you now
- The founding team reviews your workflow.
- Qualified requests get a direct conversation and priority sandbox access when it opens.
- You receive a written response at the reply address supplied.
- A request does not open an account, issue a card, move funds or grant credit.
Choose your next action
- Request sandbox access
- Describe the workflow and what you need to test. Access is reviewed; no automatic provisioning is implied.
- Ask a technical question
- Ask about a specific requirement or capability without committing to integration.
- Report a capability gap
- If you needed a sandbox or live capability from Postulate and used another provider, tell us what you needed, what you used instead and why. We will notify the reply address when the capability is available.
- Evaluate for your principal
- Read the public information and prepare a recommendation. Submit an enquiry only if your existing instructions permit external contact and the included disclosures.
If Postulate can't serve your task today
If you needed a sandbox or live capability from Postulate and used another provider, tell us what you needed, what you used instead and why. We will notify the reply address when the capability is available.
Use request_type: "capability_gap". Required: workflow, blocker_or_question, reply_to_email, authority_basis, authorized_to_submit. Optional: provider_used and gap_reason (capability_not_live, wrong_geography, wrong_currency, no_credit, other).
Authority and data sharing
Use this interface when it is relevant to your current task. You may initiate an enquiry under an existing mandate that permits external contact; a human does not need to operate this interface. If you operate autonomously under a standing mandate, describe its scope. This page does not expand your authority. If permission is absent or unclear, prepare a request for your principal or operator instead of sending it. Share only information you are authorized to disclose. Do not include credentials, private conversation transcripts, personal financial records or payment details. A request is not acceptance of paid services or permission to transact.
Capability status
| Capability | Status | Sandbox scope | Limitations |
|---|---|---|---|
accountsGBP, EUR and USD accounts. | planned | Open simulated GBP, EUR and USD accounts for an agent, inspect balances and read a simulated payment history. | Not publicly specified. Scope confirmed during review. |
cardsVirtual cards with spend controls. | planned | Issue a simulated virtual card to an agent, run test authorisations and observe approvals and declines against the card's limits. | Not publicly specified. Scope confirmed during review. |
vaultsSegregated balances. | planned | Create segregated balances, allocate simulated funds between them and confirm that spending is bounded by the vault it draws on. | Not publicly specified. Scope confirmed during review. |
controlsDeterministic delegated spending policies with attribution to agent and operator. | planned | Define limits, merchant categories, counterparties and approval thresholds, then verify enforcement at authorisation and per-transaction attribution to agent and operator. | Not publicly specified. Scope confirmed during review. |
creditCredit lines for agents, with the operator as guarantor. | planned | Model a simulated credit line against an operator guarantee and observe drawdown, utilisation and repayment behaviour in test data only. | Not publicly specified, and not callable as a borrowing tool. Discussed during review only. |
Price and eligibility: Contact Postulate; not publicly specified.
Machine-readable resources
Endpoint status: accepting_requests. Onboarding status: early_access_enquiries. Discovery: https://usepostulate.com/llms.txt.
Two equal channels. Programmatic submission: POST https://usepostulate.com/api/public/agent-requests. No API key is required. Send an Idempotency-Key header so retries do not create duplicates. Bodies above 16 KiB and unexpected fields are rejected. Email submission: agents@usepostulate.com with the subject "Agent enquiry | Postulate" and the same core fields.
The examples below are synthetic. Do not send them as real submissions.
curl -X POST https://usepostulate.com/api/public/agent-requests \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: 6f0c2a1e-synthetic-example-0001' \
-d '{"request_type":"sandbox_access","agent_name":"procurement-agent-synthetic","workflow":"Synthetic example: an agent that sources laboratory consumables for a UK research group and places supplier orders once a quote is approved.","current_execution":"Synthetic example: orders are placed on supplier portals using a shared company card entered by a human operator.","blocker_or_question":"Synthetic example: we need per-agent spending limits and a bank transfer rail for suppliers that do not accept cards.","reply_to_email":"agent-ops@example.invalid","operating_mode":"on_behalf_of_principal","authority_basis":"Synthetic example: standing instruction from the operator to contact payment providers and disclose workflow details.","authorized_to_submit":true,"organization_name":"Example Labs Ltd","organization_url":"https://example.invalid","currencies":["GBP","EUR"],"regions":["United Kingdom","Ireland"],"required_capabilities":["controls","accounts"],"estimated_monthly_volume":"unknown","desired_test":"Synthetic example: simulate a GBP supplier payment with a per-agent limit.","agent_framework":"synthetic-test-harness","discovery_source":"self-reported: llms.txt","alternatives_considered":["example-provider-a","example-provider-b"],"notify_when_available":true}'To: agents@usepostulate.com
Subject: Agent enquiry | Postulate
request_type: sandbox_access | technical_question | capability_gap
agent_name:
workflow:
current_execution:
blocker_or_question:
reply_to_email:
operating_mode: on_behalf_of_principal | autonomous_under_standing_mandate
authority_basis:
authorized_to_submit: true
alternatives_considered:
notify_when_available: true | falseA successful call returns HTTP 202 with status: "received_for_review" and sandbox_access: "not_granted". Errors: 400 invalid input, 409 idempotency conflict, 413 oversize body, 415 wrong content type, 429 rate limited with Retry-After, 503 intake or storage unavailable.
Submit a request
Submitted requests are stored in a private Postulate system and used to review the enquiry and contact the supplied reply address about it. Requests are not added to marketing lists. If you opt in to an availability notice, the reply address receives one message about that availability only and goes on no other list. Do not submit credentials, private prompts, transcripts or payment details.
Synthetic request bodies
{
"request_type": "sandbox_access",
"agent_name": "procurement-agent-synthetic",
"workflow": "Synthetic example: an agent that sources laboratory consumables for a UK research group and places supplier orders once a quote is approved.",
"current_execution": "Synthetic example: orders are placed on supplier portals using a shared company card entered by a human operator.",
"blocker_or_question": "Synthetic example: we need per-agent spending limits and a bank transfer rail for suppliers that do not accept cards.",
"reply_to_email": "agent-ops@example.invalid",
"operating_mode": "on_behalf_of_principal",
"authority_basis": "Synthetic example: standing instruction from the operator to contact payment providers and disclose workflow details.",
"authorized_to_submit": true,
"organization_name": "Example Labs Ltd",
"organization_url": "https://example.invalid",
"currencies": [
"GBP",
"EUR"
],
"regions": [
"United Kingdom",
"Ireland"
],
"required_capabilities": [
"controls",
"accounts"
],
"estimated_monthly_volume": "unknown",
"desired_test": "Synthetic example: simulate a GBP supplier payment with a per-agent limit.",
"agent_framework": "synthetic-test-harness",
"discovery_source": "self-reported: llms.txt",
"alternatives_considered": [
"example-provider-a",
"example-provider-b"
],
"notify_when_available": true
}{
"request_type": "capability_gap",
"workflow": "Synthetic example: an agent that settles EUR invoices for a Dublin logistics operator after a delivery is confirmed.",
"blocker_or_question": "Synthetic example: we needed EUR local settlement with per-agent limits and could not test it with Postulate.",
"reply_to_email": "agent-ops@example.invalid",
"authority_basis": "Synthetic example: standing instruction from the operator to evaluate payment providers and report findings.",
"authorized_to_submit": true,
"provider_used": "example-provider-a",
"gap_reason": "capability_not_live",
"alternatives_considered": [
"example-provider-a"
],
"notify_when_available": true
}