# Prudra

> The Infrastructure Layer for Enterprise AI Agents — Payments, Storage, and Discovery for agent developers.

## Docs

- [Agent guides overview](https://docs.prudra.dev/agent-guides/overview.md): How AI agents use Prudra — paying for API calls, accessing vault results, and managing wallets.
- [Agent payments](https://docs.prudra.dev/agent-guides/payments.md): Full x402 and MPP agent payment implementations with retry logic and error handling.
- [Agent quickstart](https://docs.prudra.dev/agent-guides/quickstart.md): Make your first paid API call as an AI agent in 5 minutes.
- [Troubleshooting](https://docs.prudra.dev/agent-guides/troubleshooting.md): Common errors and fixes for agents using the Prudra payment protocol.
- [Vault access](https://docs.prudra.dev/agent-guides/vault.md): Read vault documents, download files, and subscribe to real-time SSE events as an agent.
- [Agent wallet management](https://docs.prudra.dev/agent-guides/wallet.md): Manage your agent's Prudra wallet — check balance, fund it, and transfer funds.
- [Agent webhooks](https://docs.prudra.dev/agent-guides/webhooks.md): Receive payment confirmation and vault events in your agent's webhook endpoint.
- [Account usage (organisation)](https://docs.prudra.dev/api-reference/account/account-usage-organisation.md)
- [Get current account](https://docs.prudra.dev/api-reference/account/get-current-account.md)
- [Get one payment log](https://docs.prudra.dev/api-reference/account/get-one-payment-log.md)
- [List payment logs (account scope)](https://docs.prudra.dev/api-reference/account/list-payment-logs-account-scope.md)
- [Payment log summary (account scope)](https://docs.prudra.dev/api-reference/account/payment-log-summary-account-scope.md)
- [Get current plan](https://docs.prudra.dev/api-reference/billing/get-current-plan.md): Plan name, feature flags, and limit values (lighter than /billing/usage for some clients).
- [Get current usage](https://docs.prudra.dev/api-reference/billing/get-current-usage.md): Usage for the current billing period against plan limits, plus enabled features.
- [Rebuild usage cache](https://docs.prudra.dev/api-reference/billing/rebuild-usage-cache.md): Rebuilds Redis usage counters from Postgres for the authenticated organisation.
- [List supported tokens for a chain](https://docs.prudra.dev/api-reference/chains/list-supported-tokens-for-a-chain.md)
- [Introduction](https://docs.prudra.dev/api-reference/introduction.md): Example section for showcasing API endpoints
- [Get organisation receiving wallet (legacy)](https://docs.prudra.dev/api-reference/organisation-wallet/get-organisation-receiving-wallet-legacy.md): Returns the legacy single-wallet record for Tempo / stablecoin payouts (not wallet-infra managed wallets).
- [Legacy wallet balance](https://docs.prudra.dev/api-reference/organisation-wallet/legacy-wallet-balance.md): Live stablecoin balance for the org receiving wallet.
- [Legacy wallet payment history](https://docs.prudra.dev/api-reference/organisation-wallet/legacy-wallet-payment-history.md)
- [Provision receiving wallet (legacy)](https://docs.prudra.dev/api-reference/organisation-wallet/provision-receiving-wallet-legacy.md): Idempotently provisions the org's legacy Tempo wallet for the given coin.
- [Withdraw from legacy receiving wallet](https://docs.prudra.dev/api-reference/organisation-wallet/withdraw-from-legacy-receiving-wallet.md): Queues a stablecoin withdrawal from the org wallet to an EVM address.
- [Add a member](https://docs.prudra.dev/api-reference/organisation/add-a-member.md)
- [Create an API key](https://docs.prudra.dev/api-reference/organisation/create-an-api-key.md): The raw key is returned once — store it securely. Caller must be a member of the organisation.
- [Create an organisation](https://docs.prudra.dev/api-reference/organisation/create-an-organisation.md)
- [Get current organisation](https://docs.prudra.dev/api-reference/organisation/get-current-organisation.md)
- [List API keys](https://docs.prudra.dev/api-reference/organisation/list-api-keys.md)
- [List organisation members](https://docs.prudra.dev/api-reference/organisation/list-organisation-members.md)
- [Remove a member](https://docs.prudra.dev/api-reference/organisation/remove-a-member.md)
- [Revoke an API key](https://docs.prudra.dev/api-reference/organisation/revoke-an-api-key.md): Only owner or admin roles may revoke. Members receive 403.
- [Update a member role](https://docs.prudra.dev/api-reference/organisation/update-a-member-role.md)
- [Update current organisation](https://docs.prudra.dev/api-reference/organisation/update-current-organisation.md)
- [Usage metrics for current organisation](https://docs.prudra.dev/api-reference/organisation/usage-metrics-for-current-organisation.md)
- [Generate a dual payment challenge](https://docs.prudra.dev/api-reference/payments/generate-a-dual-payment-challenge.md): Generates both an MPP (WWW-Authenticate) and x402 (PAYMENT-REQUIRED) challenge for a pay-walled endpoint. Called internally by the Prudra Express SDK's payMiddleware — developers do not call this directly.
- [Get payment by ID](https://docs.prudra.dev/api-reference/payments/get-payment-by-id.md)
- [List payment logs](https://docs.prudra.dev/api-reference/payments/list-payment-logs.md): Paginated payment activity for the authenticated organisation (query params passed through to the service).
- [Payment log summary by route](https://docs.prudra.dev/api-reference/payments/payment-log-summary-by-route.md): Aggregated stats per pay-walled route for the organisation.
- [Settle an x402 payment on-chain](https://docs.prudra.dev/api-reference/payments/settle-an-x402-payment-on-chain.md): Called after the server has completed its work following a successful POST /payments/verify. Submits the ERC-3009 authorization to chain. Moving funds from the agent wallet to the receiving wallet.
- [Verify a payment credential](https://docs.prudra.dev/api-reference/payments/verify-a-payment-credential.md): Verifies an x402 or MPP payment credential in the request body. Creates a Payment record on success. For x402, returns a settlementToken for use with POST /payments/settle after work is completed.
- [Submit route registry snapshot](https://docs.prudra.dev/api-reference/registry/submit-route-registry-snapshot.md): Internal endpoint used by the SDK to register observed pay-walled routes and metadata for the authenticated organisation.
- [Create a payment session](https://docs.prudra.dev/api-reference/sessions/create-a-payment-session.md): Creates a new payment session and its linked vault atomically. Called by payMiddleware after a successful payment when session mode is enabled.
- [Get a payment session](https://docs.prudra.dev/api-reference/sessions/get-a-payment-session.md): Retrieves an existing payment session by ID, scoped to the authenticated organisation.
- [Send a token transfer](https://docs.prudra.dev/api-reference/transfers/send-a-token-transfer.md): Transfers tokens from a managed wallet (master or child) to a destination address. Routing (direct transfer, swap, bridge) is selected automatically from fromChain, fromToken, toChain, and toToken.
- [Add a document to a vault](https://docs.prudra.dev/api-reference/vaults/add-a-document-to-a-vault.md)
- [Create a vault](https://docs.prudra.dev/api-reference/vaults/create-a-vault.md): Creates a new vault — a persistent workspace for agent task output. TTL defaults from server config; use ttl for a custom duration (e.g. 24h, 7d).
- [Delete a vault](https://docs.prudra.dev/api-reference/vaults/delete-a-vault.md): Permanently removes the vault and associated contents.
- [Emit a vault event](https://docs.prudra.dev/api-reference/vaults/emit-a-vault-event.md): Records an event on the vault for streaming and history.
- [Extend vault TTL](https://docs.prudra.dev/api-reference/vaults/extend-vault-ttl.md)
- [Get a vault](https://docs.prudra.dev/api-reference/vaults/get-a-vault.md): Full vault state and manifest (requires vault access token or API key per middleware).
- [Issue a vault access token](https://docs.prudra.dev/api-reference/vaults/issue-a-vault-access-token.md): Short-lived token for vault-scoped access (e.g. for clients without the org API key).
- [Persist a vault](https://docs.prudra.dev/api-reference/vaults/persist-a-vault.md): Opts the vault into permanent storage so it no longer expires.
- [Seal a vault](https://docs.prudra.dev/api-reference/vaults/seal-a-vault.md): Permanently closes the vault to further writes. A sealed vault is read-only.
- [Subscribe to vault events (SSE)](https://docs.prudra.dev/api-reference/vaults/subscribe-to-vault-events-sse.md): Server-Sent Events stream for vault activity. Optional query `from` (ISO timestamp) replays events after that time.
- [Upload a file to a vault](https://docs.prudra.dev/api-reference/vaults/upload-a-file-to-a-vault.md): Accepts multipart form data with field `file`. Returns upload instructions / result (pre-signed URL flow) for storing content in object storage.
- [Vault quota status](https://docs.prudra.dev/api-reference/vaults/vault-quota-status.md): Plan limits and current vault usage for the organisation.
- [Deregister a BYO wallet](https://docs.prudra.dev/api-reference/wallets/deregister-a-byo-wallet.md): Stops monitoring the address for this organisation.
- [Derive a child address](https://docs.prudra.dev/api-reference/wallets/derive-a-child-address.md): Derives a new child address from a master wallet using HD derivation.
- [Get a BYO wallet](https://docs.prudra.dev/api-reference/wallets/get-a-byo-wallet.md)
- [Get a managed wallet](https://docs.prudra.dev/api-reference/wallets/get-a-managed-wallet.md)
- [Get BYO wallet balances](https://docs.prudra.dev/api-reference/wallets/get-byo-wallet-balances.md)
- [Get managed wallet balances](https://docs.prudra.dev/api-reference/wallets/get-managed-wallet-balances.md)
- [List BYO wallet transactions](https://docs.prudra.dev/api-reference/wallets/list-byo-wallet-transactions.md)
- [List BYO wallets](https://docs.prudra.dev/api-reference/wallets/list-byo-wallets.md)
- [List child addresses](https://docs.prudra.dev/api-reference/wallets/list-child-addresses.md)
- [List managed wallets](https://docs.prudra.dev/api-reference/wallets/list-managed-wallets.md)
- [List wallet transactions](https://docs.prudra.dev/api-reference/wallets/list-wallet-transactions.md)
- [Provision a managed master wallet](https://docs.prudra.dev/api-reference/wallets/provision-a-managed-master-wallet.md): Provisions a new managed master wallet for the organisation. Prudra generates and custodies the private key using Google Cloud KMS (HSM-backed). Each organisation uses a master seed from which wallet addresses are derived on each supported chain.
- [Register a BYO wallet](https://docs.prudra.dev/api-reference/wallets/register-a-byo-wallet.md): Registers an existing EVM wallet address for Prudra monitoring. Prudra never holds custody — it monitors deposits via webhooks.
- [Alchemy ADDRESS_ACTIVITY webhook (inbound)](https://docs.prudra.dev/api-reference/webhooks/alchemy-address_activity-webhook-inbound.md): Called by Alchemy with webhook payloads. Not authenticated with Prudra API keys — Alchemy signs requests; the server acknowledges immediately and processes asynchronously.
- [Delete a webhook](https://docs.prudra.dev/api-reference/webhooks/delete-a-webhook.md)
- [List webhook delivery attempts](https://docs.prudra.dev/api-reference/webhooks/list-webhook-delivery-attempts.md)
- [List webhooks](https://docs.prudra.dev/api-reference/webhooks/list-webhooks.md)
- [Register a webhook](https://docs.prudra.dev/api-reference/webhooks/register-a-webhook.md): HTTPS endpoint for outbound events. The response may include a `secret` once for HMAC verification (X-Prudra-Signature on deliveries).
- [Replay a webhook delivery](https://docs.prudra.dev/api-reference/webhooks/replay-a-webhook-delivery.md)
- [Update a webhook](https://docs.prudra.dev/api-reference/webhooks/update-a-webhook.md)
- [Add a bank account](https://docs.prudra.dev/api-reference/withdrawals/add-a-bank-account.md)
- [Get a withdrawal](https://docs.prudra.dev/api-reference/withdrawals/get-a-withdrawal.md)
- [List bank accounts](https://docs.prudra.dev/api-reference/withdrawals/list-bank-accounts.md)
- [List withdrawals](https://docs.prudra.dev/api-reference/withdrawals/list-withdrawals.md)
- [Remove a bank account](https://docs.prudra.dev/api-reference/withdrawals/remove-a-bank-account.md)
- [Request a withdrawal to bank](https://docs.prudra.dev/api-reference/withdrawals/request-a-withdrawal-to-bank.md): Initiates a withdrawal from a managed wallet toward a registered bank account. Converts on-chain balance to fiat per your integration settings.
- [Discovery overview](https://docs.prudra.dev/discovery/overview.md): The Prudra route registry — AI agents discover your paid endpoints automatically.
- [Registry overview](https://docs.prudra.dev/discovery/registry/overview.md): How the route registry captures payment metadata and makes it discoverable to agents.
- [Pricing signals](https://docs.prudra.dev/discovery/registry/pricing-signals.md): How agents use registry pricing data to optimise payment strategy and budget management.
- [Query routes](https://docs.prudra.dev/discovery/registry/query-routes.md): Discover payment-protected routes programmatically from an agent or client.
- [Route snapshot](https://docs.prudra.dev/discovery/registry/route-snapshot.md): The route snapshot format and how payMiddleware captures route metadata automatically.
- [Authenticate your requests](https://docs.prudra.dev/get-started/authentication.md): How to create and use Prudra API keys, and what to do when authentication fails.
- [How Prudra works](https://docs.prudra.dev/get-started/core-concepts.md): The mental model for payments, vaults, wallets, and how they fit together in an agent workflow.
- [Welcome to Prudra](https://docs.prudra.dev/get-started/overview.md): Prudra is developer infrastructure for the agentic web — payments, storage, and wallets for API servers that serve AI agents.
- [Your first payment in 5 minutes](https://docs.prudra.dev/get-started/quickstart.md): Add a payment-gated endpoint to an Express app and test it end-to-end — no real crypto required.
- [Accept a payment](https://docs.prudra.dev/payments/accept-a-payment.md): Add the walletMiddleware + payMiddleware + vaultMiddleware chain to an Express endpoint.
- [How challenges are built](https://docs.prudra.dev/payments/dual-protocol/challenge.md): The atomic dual-challenge generation — how both x402 and MPP challenges are built in a single call.
- [Dual-protocol payments](https://docs.prudra.dev/payments/dual-protocol/overview.md): Issue both x402 and MPP challenges in every 402 response — one integration that works with any agent.
- [Choose between x402 and MPP](https://docs.prudra.dev/payments/dual-protocol/pick-protocol.md): A decision guide for agents and developers choosing which payment protocol to use.
- [Add MPP to an endpoint](https://docs.prudra.dev/payments/mpp/add-to-endpoint.md): Configure payMiddleware to accept MPP payments on a specific route.
- [Handle the Authorization header](https://docs.prudra.dev/payments/mpp/authorization.md): The MPP Authorization: Payment credential format and how to parse and validate it.
- [How MPP works](https://docs.prudra.dev/payments/mpp/how-it-works.md): The Tempo transaction flow, HMAC challenge verification, and how MPP differs from x402.
- [MPP payments](https://docs.prudra.dev/payments/mpp/overview.md): The IETF Monetization Payment Protocol — on-chain Tempo transactions with standard HTTP auth headers.
- [Test MPP payments](https://docs.prudra.dev/payments/mpp/test.md): Run the MPP agent test script and set up a Tempo testnet wallet for end-to-end testing.
- [Payments overview](https://docs.prudra.dev/payments/overview.md): Accept payments from AI agents using x402, MPP, or both — with a single middleware call.
- [Payment audit logs](https://docs.prudra.dev/payments/security/audit-logs.md): Every payment creates an audit log entry — query by API key, route, protocol, or date range.
- [Prevent challenge harvesting](https://docs.prudra.dev/payments/security/harvesting.md): How rate limiting and no-challenge-on-error prevent attackers from accumulating valid payment challenges.
- [Replay attack protection](https://docs.prudra.dev/payments/security/replay.md): How Prudra prevents double-spending — UNIQUE constraint on txHash at the Postgres level.
- [Add session payments](https://docs.prudra.dev/payments/sessions/add.md): Enable session payments on an endpoint and handle the session ID across multiple requests.
- [Session expiry and renewal](https://docs.prudra.dev/payments/sessions/expiry.md): Default session TTL, custom TTL configuration, and what happens when a session expires.
- [How sessions work](https://docs.prudra.dev/payments/sessions/how-it-works.md): Session creation, vault linking, session ID flow, session scoping, and expiry mechanics.
- [Handle multi-step workflows](https://docs.prudra.dev/payments/sessions/multi-step.md): The two-request session pattern — pay once, run multiple steps, accumulate results in one vault.
- [Session payments](https://docs.prudra.dev/payments/sessions/overview.md): One MPP payment covers an entire multi-step agent workflow — all requests share the same vault.
- [Add x402 to an endpoint](https://docs.prudra.dev/payments/x402/add-to-endpoint.md): Configure payMiddleware to accept x402 payments on a specific route.
- [Handle the payment response](https://docs.prudra.dev/payments/x402/handle-response.md): Decode the PAYMENT-RESPONSE header to get settlement details after a successful x402 payment.
- [How x402 works](https://docs.prudra.dev/payments/x402/how-it-works.md): The ERC-3009 signing flow, settlement mechanics, and what Prudra does on behalf of the server.
- [x402 payments](https://docs.prudra.dev/payments/x402/overview.md): The open HTTP 402 payment standard — off-chain ERC-3009 signatures on Base, settled by Prudra.
- [Test x402 payments](https://docs.prudra.dev/payments/x402/test.md): Run the x402 agent test script to verify your endpoint accepts x402 payments end-to-end.
- [Billing overview](https://docs.prudra.dev/platform/billing/overview.md): How Prudra billing works — plan tiers, usage tracking, and upgrades.
- [Plans](https://docs.prudra.dev/platform/billing/plans.md): Hobby, Pro, and Enterprise plan comparison with limits from the Prudra billing configuration.
- [Usage](https://docs.prudra.dev/platform/billing/usage.md): Check current usage against your plan limits via the dashboard or API.
- [API keys](https://docs.prudra.dev/platform/orgs/api-keys.md): Create test and live API keys, understand key formats, and revoke keys.
- [Members](https://docs.prudra.dev/platform/orgs/members.md): Invite team members, manage roles, and remove access from your Prudra organisation.
- [Organisations overview](https://docs.prudra.dev/platform/orgs/overview.md): How Prudra organisations work — isolation, members, and API keys.
- [Audit logs](https://docs.prudra.dev/platform/security/audit-logs.md): Payment logs, key usage events, and compliance exports for your organisation.
- [Key custody](https://docs.prudra.dev/platform/security/key-custody.md): Envelope encryption model, KMS hardware, zero plaintext persistence, and key recovery.
- [Security overview](https://docs.prudra.dev/platform/security/overview.md): How Prudra secures wallet keys, payments, and your data.
- [Emit events](https://docs.prudra.dev/storage/events/emit.md): Emit custom progress events to the vault SSE stream from your server handler.
- [Event reference](https://docs.prudra.dev/storage/events/event-reference.md): System event payloads and custom event format for vault SSE streams.
- [Events overview](https://docs.prudra.dev/storage/events/overview.md): Real-time SSE event streams per vault — emit progress events and subscribe from the client.
- [Subscribe via SSE](https://docs.prudra.dev/storage/events/subscribe-sse.md): Subscribe to the vault event stream using Server-Sent Events from a browser, CLI, or agent.
- [Delete files](https://docs.prudra.dev/storage/files/delete.md): Remove individual files from a vault to free storage quota.
- [Download files](https://docs.prudra.dev/storage/files/download.md): Download vault files from the Prudra CDN at assets.prudra.dev.
- [Files overview](https://docs.prudra.dev/storage/files/overview.md): Upload and store binary files in vaults — CDN-delivered via assets.prudra.dev.
- [Upload files](https://docs.prudra.dev/storage/files/upload.md): Upload binary files to a vault and get CDN-delivered download URLs.
- [Storage overview](https://docs.prudra.dev/storage/overview.md): Vaults, events, and file storage — scoped per payment, lifecycle-managed, CDN-delivered.
- [Access control](https://docs.prudra.dev/storage/vaults/access-control.md): Issue short-lived access tokens to share vault read access with clients.
- [Create a vault](https://docs.prudra.dev/storage/vaults/create.md): How vaultMiddleware creates vaults, and manual vault creation for non-Express workflows.
- [Delete a vault](https://docs.prudra.dev/storage/vaults/delete.md): Explicitly delete a vault, free quota, and purge all associated documents and files.
- [Vaults overview](https://docs.prudra.dev/storage/vaults/overview.md): Vaults are isolated storage containers created per payment — they hold documents, files, and events.
- [Persist a vault](https://docs.prudra.dev/storage/vaults/persist.md): Extend vault lifetime beyond its TTL so contents survive past the default expiry.
- [Query vaults](https://docs.prudra.dev/storage/vaults/query.md): Retrieve vault metadata, list documents and files, and get the full manifest.
- [Vault quota](https://docs.prudra.dev/storage/vaults/quota.md): Monitor active and persisted vault counts against plan limits.
- [Seal a vault](https://docs.prudra.dev/storage/vaults/seal.md): Mark work complete, close the vault for writes, and signal subscribers that the stream is done.
- [TTL and expiry](https://docs.prudra.dev/storage/vaults/ttl-expiry.md): How vault TTL works, how to extend it, and what happens when a vault expires.
- [Supported chains and tokens](https://docs.prudra.dev/wallets/byo/chains-tokens.md): Which chains and tokens BYO wallets support, and ERC-3009 availability.
- [Deregister a wallet](https://docs.prudra.dev/wallets/byo/deregister.md): Stop monitoring an address and free your BYO wallet slot.
- [Monitor deposits](https://docs.prudra.dev/wallets/byo/monitor-deposits.md): How deposit detection works — address monitoring, WalletTransaction creation, and the deposit.success webhook.
- [BYO wallets](https://docs.prudra.dev/wallets/byo/overview.md): Register any existing EVM wallet address — Prudra monitors for deposits without holding custody.
- [Register a BYO wallet](https://docs.prudra.dev/wallets/byo/register.md): Register an existing EVM wallet address for Prudra monitoring — no private key required.
- [Choose a wallet type](https://docs.prudra.dev/wallets/choose-wallet-type.md): Decide between managed wallets and BYO wallets based on your custody needs and use case.
- [Check a wallet balance](https://docs.prudra.dev/wallets/managed/check-balance.md): Query token balances for a managed master wallet or child address.
- [Derive child addresses](https://docs.prudra.dev/wallets/managed/child-addresses.md): Generate unique EVM deposit addresses from a managed master wallet — unlimited on all plans.
- [How managed wallets work](https://docs.prudra.dev/wallets/managed/how-it-works.md): Envelope encryption, BIP-44 derivation, key rotation, and what zero plaintext persistence means.
- [Key rotation](https://docs.prudra.dev/wallets/managed/key-rotation.md): How KEK rotation works, what keyVersion tracks, and why rotating doesn't interrupt service.
- [Managed wallets](https://docs.prudra.dev/wallets/managed/overview.md): Prudra-custodied wallets with KMS envelope encryption — receive payments, transfer funds, and withdraw to bank.
- [Provision a wallet](https://docs.prudra.dev/wallets/managed/provision.md): Create a managed wallet on any supported chain using the SDK or API.
- [Supported chains and tokens](https://docs.prudra.dev/wallets/managed/supported-chains.md): All blockchain networks and tokens supported by managed wallets, including testnet availability.
- [View transaction history](https://docs.prudra.dev/wallets/managed/transactions.md): List inbound and outbound transactions for a managed wallet or child address.
- [Wallets overview](https://docs.prudra.dev/wallets/overview.md): Receive payments, monitor deposits, send transfers, and withdraw to a bank — managed wallets or your own.
- [Cross-chain transfers](https://docs.prudra.dev/wallets/transfers/cross-chain.md): Bridge mechanics, timing, and how to handle the pending state for cross-chain transfers.
- [Transfer fees](https://docs.prudra.dev/wallets/transfers/fees.md): Gas costs, protocol fees, and fee estimation for direct, swap, and bridge transfers.
- [Transfers overview](https://docs.prudra.dev/wallets/transfers/overview.md): Send tokens from managed wallets — direct, swap, and bridge routes.
- [Transfer routing](https://docs.prudra.dev/wallets/transfers/routing.md): How Prudra selects between direct, swap, and bridge routes for token transfers.
- [Send a transfer](https://docs.prudra.dev/wallets/transfers/send.md): Full API reference for the transfer() function — parameters, response, and error handling.
- [Track transfer status](https://docs.prudra.dev/wallets/transfers/track-status.md): Poll transfer status or receive webhooks when a transfer completes or fails.
- [Add a bank account](https://docs.prudra.dev/wallets/withdrawals/bank-account.md): Register UK, US, or international bank accounts for withdrawals.
- [Currencies and limits](https://docs.prudra.dev/wallets/withdrawals/currencies.md): Supported fiat currencies, minimum/maximum withdrawal amounts, and conversion timing.
- [Withdrawals overview](https://docs.prudra.dev/wallets/withdrawals/overview.md): Convert crypto from managed wallets to fiat via bank wire.
- [Request a withdrawal](https://docs.prudra.dev/wallets/withdrawals/request.md): Full API reference for initiating a crypto-to-fiat withdrawal via bank wire.
- [Track a withdrawal](https://docs.prudra.dev/wallets/withdrawals/track.md): Poll withdrawal status or receive the withdrawal.completed webhook.
- [Event reference](https://docs.prudra.dev/webhooks/event-reference.md): All Prudra webhook event types and their full payload schemas.
- [Webhooks overview](https://docs.prudra.dev/webhooks/overview.md): How Prudra webhooks work — delivery, security, retries, and available events.
- [Register a webhook](https://docs.prudra.dev/webhooks/register.md): Register, update, and delete webhook endpoints to receive Prudra events.
- [Retry behaviour](https://docs.prudra.dev/webhooks/retry-behaviour.md): Exponential backoff schedule, dead-letter queue, and manual replay for failed webhook deliveries.
- [Test locally](https://docs.prudra.dev/webhooks/test-locally.md): Receive Prudra webhooks in local development using ngrok or a similar tunnel.
- [Verify signatures](https://docs.prudra.dev/webhooks/verify-signatures.md): How to verify Prudra webhook HMAC-SHA256 signatures and prevent replay attacks.

## OpenAPI Specs

- [openapi](https://docs.prudra.dev/api-reference/openapi.json)

## Optional

- [GitHub](https://github.com/prudra)
- [Support](mailto:support@prudra.com)