# Polygon Developer Docs

## Docs

- [Polygon Developer Docs](https://docs.polygon.technology/index.md): Polygon developer documentation: the Open Money Stack API for stablecoin payments, non-custodial wallets, on-ramps and off-ramps, cross-chain settlement, and the Polygon Chain, CDK, and Agglayer infrastructure that powers it.
- [What is the Open Money Stack?](https://docs.polygon.technology/oms/overview.md): The Open Money Stack is Polygon's stablecoin payments infrastructure: fiat on-ramps and off-ramps, wallet infrastructure, compliance, stablecoin orchestration, and onchain settlement in one open, vertically integrated platform.
- [Get started](https://docs.polygon.technology/payments/get-started.md): Request access, authenticate, and run your first transaction on the Open Money Stack.
- [USD stablecoin accounts for global users](https://docs.polygon.technology/payments/use-cases/dollar-accounts.md): Give customers in any country a real USD account number for ACH transfers, backed by USDC on Polygon. Dollar banking and stablecoin-backed accounts without a US bank or correspondent banking chain.
- [Payroll and contractor disbursements](https://docs.polygon.technology/payments/use-cases/payroll-disbursements.md): Pay workers and contractors in their local currency from a single USDC treasury wallet.
- [Consumer on-ramp and off-ramp](https://docs.polygon.technology/payments/use-cases/consumer-on-offramp.md): Fund a crypto wallet via cash-in or bank rails, and withdraw back to a bank.
- [Stablecoin rewards and loyalty](https://docs.polygon.technology/payments/use-cases/rewards-loyalty.md): Drop USDC rewards, cashback, and loyalty balances directly into user wallets on Polygon. Programmable stablecoin rewards with no card networks, no breakage, and no expiry.
- [Stablecoin cross-border remittance](https://docs.polygon.technology/payments/use-cases/cross-border-remittance.md): Build cross-border remittance products on stablecoin rails: fiat in, fiat out, settled on Polygon in minutes instead of days. Skip the correspondent banking chain and the 5-7% fee.
- [Customer onboarding](https://docs.polygon.technology/payments/guides/customer-onboarding.md): How to register a customer, collect identity verification, and provision their first wallet.
- [Receiving webhooks](https://docs.polygon.technology/payments/guides/receiving-webhooks.md): Build an endpoint that verifies OMS webhook deliveries and applies them safely, without double-processing or applying stale state.
- [Fiat to crypto](https://docs.polygon.technology/payments/guides/fiat-to-crypto.md): How to bring fiat into a customer's custodial wallet.
- [Bank transfers](https://docs.polygon.technology/api-reference/guide-bank-transfers.md): How to move money between bank accounts and OMS wallets in both directions.
- [Cash-in](https://docs.polygon.technology/api-reference/guide-cash-in.md): How to let a customer deposit physical cash at a retail location and receive USDC in their wallet.
- [Virtual accounts](https://docs.polygon.technology/payments/guides/virtual-accounts.md): How to give a customer a dedicated bank account number that auto-converts incoming fiat deposits to crypto.
- [Deposit addresses](https://docs.polygon.technology/payments/guides/deposit-addresses.md): How to accept crypto at a persistent on-chain address that auto-converts incoming funds and pays out to a bank account.
- [Send from a wallet](https://docs.polygon.technology/payments/guides/crypto-to-fiat.md): Use the quote and transaction flow to move USDC out of a custodial wallet to a crypto address or a bank account.
- [Pay a third party](https://docs.polygon.technology/payments/guides/third-party-payouts.md): Register a counterparty and their bank account, then pay them from a customer's wallet with the quote and transaction flow.
- [Cash pickup](https://docs.polygon.technology/api-reference/guide-cash-pickup.md): Let a customer withdraw crypto as physical cash at a retail or ATM location.
- [Bulk payouts](https://docs.polygon.technology/api-reference/guide-b2b-payouts.md): Disburse stablecoin or fiat payments to multiple recipients from a platform treasury wallet.
- [Global remittance](https://docs.polygon.technology/api-reference/guide-global-remittance.md): Cross-border money transfer: fiat in, stablecoin settlement on Polygon, fiat out.
- [Entities and relationships](https://docs.polygon.technology/payments/core-concepts/entities.md): The core resources in OMS and how they relate to each other.
- [Quote system](https://docs.polygon.technology/payments/core-concepts/quote-system.md): How OMS locks pricing, structures fees, and calculates exchange rates.
- [Account model](https://docs.polygon.technology/payments/core-concepts/account-model.md): OMS supports custodial, non-custodial, and agentic custody models. This page covers the account types used by the custodial model.
- [Transaction lifecycle](https://docs.polygon.technology/payments/core-concepts/transaction-lifecycle.md): How a transaction moves through OMS from creation to completion, including statuses, sub-statuses, and webhook events.
- [Currencies and rails](https://docs.polygon.technology/payments/core-concepts/currencies-and-rails.md): Supported assets, networks, and payment rails in OMS.
- [Sandbox and testing](https://docs.polygon.technology/payments/core-concepts/sandbox-and-testing.md): How the OMS sandbox environment works, how networks map to testnets, and how to simulate inbound events.
- [Open Money Stack Payments API](https://docs.polygon.technology/payments/overview.md): Open Money Stack Payments API: fiat-to-crypto and crypto-to-fiat on-ramps, custodial wallets, compliance, and stablecoin orchestration in a single integration. ACH, wire, SWIFT, cash, and card rails.
- [Explore Money Flows](https://docs.polygon.technology/payments/payment-flows.md): Interactive visualization of OMS payment flows and transaction routing.
- [Customers](https://docs.polygon.technology/payments/customers.md): Identity records that own wallets and transactions in OMS.
- [Transactions](https://docs.polygon.technology/payments/transactions.md): The core money movement operation in OMS: quote, then execute.
- [Deposit addresses](https://docs.polygon.technology/payments/deposit-addresses.md): Reusable on-chain addresses that auto-convert incoming crypto and pay out to a bank account.
- [Virtual accounts](https://docs.polygon.technology/payments/virtual-accounts.md): Dedicated bank account numbers that auto-convert incoming fiat to crypto.
- [Cash-ins and cash-outs](https://docs.polygon.technology/payments/cash-ins-and-cash-outs.md): Code-based cash deposits and withdrawals at retail locations, auto-converted between cash and crypto.
- [External accounts](https://docs.polygon.technology/payments/external-accounts.md): Off-platform bank accounts, external wallets, and debit cards, referenced by ID on a quote.
- [Debit cards](https://docs.polygon.technology/payments/debit-cards.md): Use a debit card as an on-ramp funding source or an off-ramp payout destination in OMS.
- [Stablecoins](https://docs.polygon.technology/payments/stablecoins.md): Overview of stablecoins available on Polygon Chain, with integration guides for USDC and cross-chain transfers.
- [Compliance](https://docs.polygon.technology/payments/compliance.md): How the Open Money Stack handles KYC, KYB, AML, and transaction monitoring for regulated payment products.
- [Supported Jurisdictions](https://docs.polygon.technology/payments/supported-jurisdictions-networks.md): Jurisdiction eligibility for Polygon OMS, including prohibited countries and how restrictions are enforced.
- [OMS wallets](https://docs.polygon.technology/wallets/overview.md): OMS wallets-as-a-service: custodial, non-custodial, and agentic wallets for applications. Chain-agnostic, with social login, smart sessions, and compliance built in.
- [OMS Custodial Wallets](https://docs.polygon.technology/wallets/custodial-wallets.md): Managed wallets where OMS holds and secures private keys for your users, with KYC, AML, and compliance built in.
- [Custodial wallet quickstart](https://docs.polygon.technology/wallets/custodial-wallets-quickstart.md): Authenticate, create a customer, and provision an OMS custodial wallet with the API.
- [OMS Non-Custodial Wallets](https://docs.polygon.technology/wallets/non-custodial-wallets.md): Embedded non-custodial smart contract wallets built into your app, with OIDC and email authentication, smart sessions, and no separate wallet app.
- [SDK Quickstart](https://docs.polygon.technology/wallets/quickstart.md): Install an OMS Wallet SDK, authenticate a non-custodial wallet, and send a first transaction.
- [Authentication](https://docs.polygon.technology/wallets/authentication.md): Authenticate non-custodial wallets with OIDC or email OTP.
- [Smart Sessions](https://docs.polygon.technology/wallets/smart-sessions.md): Grant a remote backend or in-app flow limited, time-bounded, revocable access to send transactions from a user's wallet, enforced on-chain.
- [Wallet Operations](https://docs.polygon.technology/wallets/wallet-operations.md): Send transactions, transfer stablecoins, sign messages, and read balances from a non-custodial wallet.
- [Private Send](https://docs.polygon.technology/wallets/private-send.md): Send funds privately from a non-custodial wallet, with the sender's identity shielded and the transaction integrity cryptographically verified end to end.
- [Recovery](https://docs.polygon.technology/wallets/recovery.md): How users recover access to their non-custodial wallet using multiple linked authentication methods and timed recovery.
- [Security](https://docs.polygon.technology/wallets/security.md): How keys are secured, transactions are validated, and the wallet remains non-custodial end to end.
- [OMS Wallet SDKs](https://docs.polygon.technology/wallets/sdk/overview.md): Choose an OMS Wallet SDK for a web, React Native, iOS, or Android application.
- [Send USDC](https://docs.polygon.technology/wallets/sdk/guides/send-usdc.md): Send USDC from an active OMS Wallet session on Polygon PoS.
- [Swap wallet assets](https://docs.polygon.technology/wallets/sdk/guides/swap.md): Choose a destination asset, quote a Trails route, and execute the intent through an active OMS Wallet session.
- [Earn with Trails](https://docs.polygon.technology/wallets/sdk/guides/earn.md): Discover an Earn market, deposit its required asset, read the resulting position, and withdraw with Trails and OMS Wallet.
- [Backend wallet verification](https://docs.polygon.technology/wallets/sdk/guides/backend-wallet-verification.md): Verify an OMS Wallet ID token on your backend against the configured token issuer JWKS.
- [TypeScript SDK quickstart](https://docs.polygon.technology/wallets/sdk/typescript/quickstart.md): Install the TypeScript OMS Wallet SDK, authenticate a wallet, and send a Polygon Amoy transaction.
- [TypeScript SDK authentication](https://docs.polygon.technology/wallets/sdk/typescript/authentication.md): Establish an OMS Wallet credential and activate a wallet with email or OIDC.
- [TypeScript sessions and access](https://docs.polygon.technology/wallets/sdk/typescript/sessions-and-access.md): Restore wallet sessions, switch wallets, issue backend tokens, manage access, and sign out.
- [Send transactions with TypeScript](https://docs.polygon.technology/wallets/sdk/typescript/send-transactions.md): Prepare, fund, execute, and track OMS Wallet transactions from TypeScript.
- [Sign and verify with TypeScript](https://docs.polygon.technology/wallets/sdk/typescript/sign-and-verify.md): Sign messages and typed data, then verify signatures for active or explicit wallets.
- [TypeScript balances and history](https://docs.polygon.technology/wallets/sdk/typescript/balances-and-history.md): Query balances and transaction history for any address without a wallet session.
- [TypeScript networks](https://docs.polygon.technology/wallets/sdk/typescript/networks-and-reference.md): Look up the networks supported by the OMS Wallet TypeScript SDK.
- [TypeScript API reference](https://docs.polygon.technology/wallets/sdk/typescript/api-reference.md): Complete public API reference for the OMS Wallet TypeScript SDK.
- [Use the TypeScript SDK with wagmi](https://docs.polygon.technology/wallets/sdk/typescript/using-with-wagmi-connector.md): Connect an active OMS Wallet session to wagmi for signing and transaction submission.
- [React Native SDK quickstart](https://docs.polygon.technology/wallets/sdk/react-native/quickstart.md): Install the React Native OMS Wallet SDK, authenticate a wallet, and send a test transaction.
- [React Native authentication](https://docs.polygon.technology/wallets/sdk/react-native/authentication.md): Authenticate with an OIDC ID token, email OTP, or an OIDC redirect and activate a wallet.
- [React Native sessions and access](https://docs.polygon.technology/wallets/sdk/react-native/sessions-and-access.md): Restore wallet sessions, manage wallets, issue wallet ID tokens, and revoke access credentials.
- [Send transactions with React Native](https://docs.polygon.technology/wallets/sdk/react-native/send-transactions.md): Send native transfers, encoded calls, and ABI contract calls through one transaction lifecycle.
- [Sign and verify with React Native](https://docs.polygon.technology/wallets/sdk/react-native/sign-and-verify.md): Sign messages and EIP-712 typed data and verify signatures against the active wallet.
- [React Native balances and history](https://docs.polygon.technology/wallets/sdk/react-native/balances-and-history.md): Query balances and transaction history for any address without an authenticated wallet session.
- [React Native networks](https://docs.polygon.technology/wallets/sdk/react-native/networks-and-reference.md): Look up the networks supported by the OMS Wallet React Native SDK.
- [React Native API reference](https://docs.polygon.technology/wallets/sdk/react-native/api-reference.md): Complete public API reference for the OMS Wallet React Native SDK.
- [Swift SDK quickstart](https://docs.polygon.technology/wallets/sdk/swift/quickstart.md): Install the Swift OMS Wallet SDK, authenticate a wallet, and send a transaction on Polygon Amoy.
- [Swift SDK authentication](https://docs.polygon.technology/wallets/sdk/swift/authentication.md): Authenticate with a provider ID token, email OTP, or an OIDC redirect and activate a wallet.
- [Swift sessions and access](https://docs.polygon.technology/wallets/sdk/swift/sessions-and-access.md): Restore wallet sessions, switch wallets, issue wallet ID tokens, and manage access credentials.
- [Send transactions with Swift](https://docs.polygon.technology/wallets/sdk/swift/send-transactions.md): Submit native transfers and contract calls through the Swift SDK transaction lifecycle.
- [Sign and verify with Swift](https://docs.polygon.technology/wallets/sdk/swift/sign-and-verify.md): Sign messages and typed data, then verify signatures with an active Swift wallet session.
- [Swift balances and history](https://docs.polygon.technology/wallets/sdk/swift/balances-and-history.md): Query native balances, contract token balances, and transaction history for any address.
- [Swift networks](https://docs.polygon.technology/wallets/sdk/swift/networks-and-reference.md): Look up the networks supported by the OMS Wallet Swift SDK.
- [Swift API reference](https://docs.polygon.technology/wallets/sdk/swift/api-reference.md): Complete public API reference for the OMS Wallet Swift SDK.
- [Kotlin SDK quickstart](https://docs.polygon.technology/wallets/sdk/kotlin/quickstart.md): Install the Kotlin SDK, authenticate a wallet, and send a transaction on Polygon Amoy.
- [Kotlin SDK authentication](https://docs.polygon.technology/wallets/sdk/kotlin/authentication.md): Authenticate with an OIDC ID token, email OTP, or OIDC redirect and activate a wallet.
- [Kotlin SDK sessions and access](https://docs.polygon.technology/wallets/sdk/kotlin/sessions-and-access.md): Restore completed sessions, switch wallets, issue backend ID tokens, and manage wallet access.
- [Kotlin SDK send transactions](https://docs.polygon.technology/wallets/sdk/kotlin/send-transactions.md): Send native value, encoded calldata, and contract calls through one transaction lifecycle.
- [Kotlin SDK sign and verify](https://docs.polygon.technology/wallets/sdk/kotlin/sign-and-verify.md): Sign messages and EIP-712 typed data, then verify signatures for the active wallet.
- [Kotlin SDK balances and history](https://docs.polygon.technology/wallets/sdk/kotlin/balances-and-history.md): Query native balances, contract-token balances, and transaction history for any address.
- [Kotlin SDK networks](https://docs.polygon.technology/wallets/sdk/kotlin/networks-and-reference.md): Look up the networks supported by the OMS Wallet Kotlin SDK.
- [Kotlin API reference](https://docs.polygon.technology/wallets/sdk/kotlin/api-reference.md): Complete public API reference for the OMS Wallet Kotlin SDK.
- [Interactive Demo](https://docs.polygon.technology/wallets/examples/interactive-demo.md): An interactive walkthrough of a neobank built on OMS wallets, using mock data.
- [Neobank iOS Demo](https://docs.polygon.technology/wallets/examples/neobank-ios.md): A white-label neobank and smart-wallet starter built on the OMS mobile wallet foundation.
- [Hosted Wallet](https://docs.polygon.technology/wallets/hosted-wallet.md): Launch a non-custodial wallet on your domain with OMS-operated infrastructure, branding control, Smart Sessions, and social or email authentication.
- [Custom Wallet](https://docs.polygon.technology/wallets/custom-wallet.md): Build a fully custom non-custodial wallet using the Wallet Development Kit on top of OMS wallet infrastructure. Self-host critical components if needed.
- [Automate USDC collection with a Treasury Wallet](https://docs.polygon.technology/wallets/treasury-wallet.md): Use OMS wallets and Smart Sessions to automate pull-and-push USDC flows from client wallets to a central treasury, with no per-transfer approvals.
- [Offer Yield Accounts to Your Users](https://docs.polygon.technology/wallets/morpho-vault-deposit.md): Add an interest-bearing savings feature to your fintech app. Users deposit funds, earn yield automatically, and withdraw at any time, with no crypto knowledge required.
- [Agentic Wallets](https://docs.polygon.technology/wallets/agentic-wallets-overview.md): Session-based smart contract wallets for AI agents that operate onchain autonomously.
- [OMS Wallet Architecture](https://docs.polygon.technology/wallets/architecture.md): How OMS Wallet works: the WaaS embedded wallet service, wallet contracts v3, smart sessions, and the Guard Firewall.
- [Smart Sessions: Technical Deep Dive](https://docs.polygon.technology/wallets/smart-sessions-deep-dive.md): How Smart Sessions work under the hood: the Sessions Module, V3 config tree placement, session keys, lazy EIP-7702 delegation, and on-chain enforcement.
- [Wallet Configuration](https://docs.polygon.technology/wallets/wallet-configuration.md): How the Merkleized wallet configuration works: single onchain root, signers, sessions, recovery, and cross-chain coherency.
- [Guard Firewall](https://docs.polygon.technology/wallets/guard-firewall.md): Ecosystem-level transaction review that evaluates every transaction against policies, threat simulations, and blacklists before allowing onchain execution.
- [OMS Wallet Infrastructure](https://docs.polygon.technology/wallets/infrastructure.md): How OMS Wallet keeps user keys non-custodial: Nitro Enclave isolation, attestation, encryption pool, Shamir-split KMS keys, and the Trusted Third Party council.
- [Timed Recovery: Technical Reference](https://docs.polygon.technology/wallets/timed-recovery-technical.md): Full technical specification of the timed recovery flow, onchain observability, Operator independence, and recovery FAQ.
- [Multi-Auth Linking](https://docs.polygon.technology/wallets/multi-auth-linking.md): Attach multiple authentication methods to a single OMS Wallet for recovery and flexibility, with security guarantees against silent cross-provider linking.
- [Supported networks](https://docs.polygon.technology/wallets/supported-networks.md): EVM networks available to OMS wallets, listed with their chain IDs.
- [Cross-chain payments, swaps, bridging, deposits, and actions](https://docs.polygon.technology/cross-chain/index.md): One Open Money Stack API for cross-chain payments, swaps, bridging, deposits, and composable onchain actions. Route customer funds from any token on any chain to any destination in one user action.
- [Use cases](https://docs.polygon.technology/cross-chain/use-cases.md): How fintechs, neobanks, banks, and marketplaces use cross-chain payment orchestration.
- [Accept funds from anywhere](https://docs.polygon.technology/cross-chain/fund.md): Let customers fund your product from a card, bank account, exchange balance, or any wallet.
- [Swap & bridge](https://docs.polygon.technology/cross-chain/swap-bridge.md): Let customers move and convert funds across any network in a single step, without managing bridges or liquidity yourself.
- [Earn accounts](https://docs.polygon.technology/cross-chain/earn.md): Offer customers a yield-bearing account powered by onchain lending markets, funded from a card or bank in one step.
- [Programmable destinations](https://docs.polygon.technology/cross-chain/money-actions.md): Execute a deposit, yield position, or any product action automatically when funds arrive.
- [SDK quickstart](https://docs.polygon.technology/cross-chain/sdk/index.md): Install the SDK and drop in a payment widget in under five minutes.
- [Composable actions](https://docs.polygon.technology/cross-chain/sdk/composable-actions/index.md): Chain multiple onchain actions into a single intent: bridge, swap, stake, and deposit in one user signature.
- [Building actions](https://docs.polygon.technology/cross-chain/sdk/composable-actions/building-actions.md): Reference for all composable action builders: swap, lend, deposit, assertCondition, and custom.
- [Dynamic values](https://docs.polygon.technology/cross-chain/sdk/composable-actions/dynamic-values.md): Use dynamic() and self() to resolve amounts and addresses at execution time.
- [Pay component](https://docs.polygon.technology/cross-chain/sdk/pay.md): Accept exact-output payments where the recipient receives a precise amount regardless of the sender's source token.
- [Swap component](https://docs.polygon.technology/cross-chain/sdk/swap.md): Cross-chain token swaps with automatic routing across bridges and DEXs.
- [Earn component](https://docs.polygon.technology/cross-chain/sdk/earn.md): Open the market selector and let users deposit into DeFi yield protocols from any chain or funding source.
- [SDK configuration](https://docs.polygon.technology/cross-chain/sdk/configuration.md): Shared props reference for all Trails widget components.
- [React hooks](https://docs.polygon.technology/cross-chain/sdk/hooks.md): Hooks for building custom payment UIs with cross-chain routing and state.
- [Solana support](https://docs.polygon.technology/cross-chain/sdk/solana.md): How widget modes handle EVM and Solana origin and destination addresses, and the automatic chain syncing that keeps them aligned.
- [Cross-chain API overview](https://docs.polygon.technology/cross-chain/api-reference/overview.md): Authentication, base URL, and the intent lifecycle for the cross-chain payments API.
- [Quotes and execution](https://docs.polygon.technology/cross-chain/api-reference/quotes.md): QuoteIntent, CommitIntent, ExecuteIntent, and AbortIntent.
- [Status and monitoring](https://docs.polygon.technology/cross-chain/api-reference/monitoring.md): Track intent status through to settlement: GetIntent, GetIntentReceipt, WaitIntentReceipt, SearchIntents, and GetIntentHistory.
- [Routes and discovery](https://docs.polygon.technology/cross-chain/api-reference/discovery.md): Discover supported networks, tokens, routes, and prices: GetChains, GetTokenList, routes, and pricing endpoints.
- [Open Money Stack API](https://docs.polygon.technology/api-reference/overview.md): How the Open Money Stack API works: core concepts, transaction types, and API structure.
- [Create a payment quote](https://docs.polygon.technology/api-reference/quote/create-a-payment-quote.md): Creates a payment quote with a locked exchange rate and fee breakdown for a prospective transfer. Quotes expire after a short window; reference the returned quote ID when executing the transaction. Pass an Idempotency-Key header to safely retry.
- [Get quote by ID](https://docs.polygon.technology/api-reference/quote/get-quote-by-id.md): Retrieves a previously created quote by ID, including its locked rate, fee breakdown, and expiry.
- [Execute a transaction (send)](https://docs.polygon.technology/api-reference/transaction/execute-a-transaction-send.md): Executes a transfer by accepting an open quote. Reference the quote by its ID; OMS pulls funds from the quote's source and delivers them to its destination. Pass an Idempotency-Key header to safely retry without sending twice.
- [List transactions with filters](https://docs.polygon.technology/api-reference/transaction/list-transactions-with-filters.md): List transactions with filters.
- [Get transaction by ID](https://docs.polygon.technology/api-reference/transaction/get-transaction-by-id.md): Retrieves a single transaction by ID.
- [Create a cash-in deposit code](https://docs.polygon.technology/api-reference/cashins/create-a-cash-in-deposit-code.md): Creates a cash-in: reserves a deposit code the customer presents at a physical cash location to deposit fiat, which is then converted to crypto and credited to the destination wallet. The 201 response includes the cash-in and its deposit instructions (the code and its expiry). Pass an Idempotency-Ke…
- [List cash-ins](https://docs.polygon.technology/api-reference/cashins/list-cash-ins.md): Returns a paginated list of cash-ins, optionally filtered by customer, status, type, date range, or free-text search. Results are ordered newest-first. Date filters `createdAfter` and `createdBefore` are inclusive, matching `GET /transactions`.
- [Get a cash-in by ID](https://docs.polygon.technology/api-reference/cashins/get-a-cash-in-by-id.md): Retrieves a single cash-in by ID, including its current status and sub-status, source and destination amounts, fees, and deposit instructions.
- [Refresh a cash-in deposit code](https://docs.polygon.technology/api-reference/cashins/refresh-a-cash-in-deposit-code.md): Regenerates the deposit code for an existing cash-in whose code has expired or is close to expiring, returning a fresh code and expiry. Pass an Idempotency-Key header to safely retry.
- [Create a Deposit Address](https://docs.polygon.technology/api-reference/depositaddress/create-a-deposit-address.md): Create a Deposit Address. Requires deposit addresses to be enabled for your project and the customer to be provisioned with the banking provider. The address starts `pending` and becomes `active` once the inbound on-chain address is assigned.
- [List all Deposit Addresses](https://docs.polygon.technology/api-reference/depositaddress/list-all-deposit-addresses.md): List all Deposit Addresses across the organization. Spans every customer in the caller's organization; optionally filter by status and/or customer.
- [Get a Deposit Address](https://docs.polygon.technology/api-reference/depositaddress/get-a-deposit-address.md): Fetch a Deposit Address by ID.
- [Update a Deposit Address](https://docs.polygon.technology/api-reference/depositaddress/update-a-deposit-address.md): Update a Deposit Address. The patchable fields are `destination` (re-point to a different bank-type External Account), `returnDestination`, `label`, and `metadata`; any other JSON key in the body is rejected with 400. Re-pointing `destination` to a healthy bank External Account recovers a DA from `i…
- [Create a Virtual Account](https://docs.polygon.technology/api-reference/virtualaccount/create-a-virtual-account.md): Create a Virtual Account for a customer. Partner must have virtual_account_provider configured.
- [List all Virtual Accounts](https://docs.polygon.technology/api-reference/virtualaccount/list-all-virtual-accounts.md): List all Virtual Accounts across the organization. Spans every customer in the caller's organization; optionally filter by status and/or customer.
- [Get a Virtual Account](https://docs.polygon.technology/api-reference/virtualaccount/get-a-virtual-account.md): Fetch a Virtual Account by ID.
- [Update a Virtual Account](https://docs.polygon.technology/api-reference/virtualaccount/update-a-virtual-account.md): Update a Virtual Account. Patchable fields: `destination` (re-point), `sponsorGas`, `label`, `metadata`; any other JSON key is rejected with 400. Re-pointing `destination` to a healthy External Account recovers a VA from `inactiveActionRequired` back to `active`.
- [Delete a Virtual Account](https://docs.polygon.technology/api-reference/virtualaccount/delete-a-virtual-account.md): Delete a customer's Virtual Account. Initiates the close flow against the underlying Erebor DDA; the VA enters the delete-pending window (status remains as-is, `deletionRequestedAt` set) and finalizes to `deleted` on the subsequent `DEPOSIT_ACCOUNT.CLOSED` webhook.
- [Create a Counterparty](https://docs.polygon.technology/api-reference/counterparty/create-a-counterparty.md): Create a Counterparty.
- [List Counterparties](https://docs.polygon.technology/api-reference/counterparty/list-counterparties.md): List Counterparties. `customerId` is an optional filter — omit it to list all counterparties in the project (still tenant-scoped by project).
- [Get a Counterparty](https://docs.polygon.technology/api-reference/counterparty/get-a-counterparty.md): Get a Counterparty by id.
- [Update a Counterparty](https://docs.polygon.technology/api-reference/counterparty/update-a-counterparty.md): Update a Counterparty (partial; unknown keys 400).
- [Delete a Counterparty](https://docs.polygon.technology/api-reference/counterparty/delete-a-counterparty.md): Delete a Counterparty (soft delete). Returns 409 when the counterparty still owns active or pending External Accounts.
- [Create an External Account](https://docs.polygon.technology/api-reference/externalaccount/create-an-external-account.md): Create an External Account (saved payment destination). Provisions synchronously against the configured payment provider; the account starts `pending` and flips to `active` or `failed`. Exactly one per-type detail object must match `type`. The owner discriminator determines whether this account belo…
- [List External Accounts](https://docs.polygon.technology/api-reference/externalaccount/list-external-accounts.md): List External Accounts. Both `customerId` and `counterpartyId` are optional filters — omit both to list all external accounts in the project (still tenant-scoped by project).
- [Get an External Account](https://docs.polygon.technology/api-reference/externalaccount/get-an-external-account.md): Get an External Account by id.
- [Update an External Account](https://docs.polygon.technology/api-reference/externalaccount/update-an-external-account.md): Update an External Account. Only `label` and `metadata` are mutable; any other JSON key in the body is rejected with 400.
- [Delete an External Account](https://docs.polygon.technology/api-reference/externalaccount/delete-an-external-account.md): Delete an External Account (soft delete).
- [Get bearer token](https://docs.polygon.technology/api-reference/auth/get-bearer-token.md): Exchanges an OMS API key + secret for a bearer token valid for 60 minutes. The token is signed by the OMS issuer and must be presented as `Authorization Bearer <token>` on every other endpoint.
- [Create a customer](https://docs.polygon.technology/api-reference/customers/create-a-customer.md)
- [List customers](https://docs.polygon.technology/api-reference/customers/list-customers.md): Returns a paginated list of customers under the current Project.
- [Get customer by ID](https://docs.polygon.technology/api-reference/customers/get-customer-by-id.md): Returns the customer with their wallets included in the response.
- [Update a customer](https://docs.polygon.technology/api-reference/customers/update-a-customer.md): Partial update. Only include fields you want to change. Compliance-relevant changes (residentialAddress, lastName, identifyingInformation, ipAddress) may trigger endorsement re-evaluation. Including endorsement names in the endorsements array explicitly triggers re-evaluation.
- [Delete a customer](https://docs.polygon.technology/api-reference/customers/delete-a-customer.md): Soft delete. Sets status to inactive. Inactive customers cannot create new transactions but data is retained for compliance purposes.
- [Get customer balance](https://docs.polygon.technology/api-reference/customer/get-customer-balance.md): Get the aggregated estimated balance across all customer wallets/assets.
- [Create a new wallet asset for a customer](https://docs.polygon.technology/api-reference/wallet/create-a-new-wallet-asset-for-a-customer.md): Provisions a crypto wallet for a customer for the requested asset and chain, returning the created wallet. Pass an Idempotency-Key header to safely retry without provisioning duplicates.
- [List customer wallets](https://docs.polygon.technology/api-reference/wallet/list-customer-wallets.md): Lists the crypto wallets provisioned for a customer (one per asset/chain), with cursor-based pagination. Returns an empty list if none have been provisioned yet.
- [Associate an embedded wallet with a customer](https://docs.polygon.technology/api-reference/wallets/associate-an-embedded-wallet-with-a-customer.md): Links an embedded (WaaS) wallet to the customer. The wallet is identified by the supplied WaaS idToken — its subject is the wallet id, so the wallet id is never passed directly — and the token's audience must be the authenticated project.
- [Get current balance of a specific wallet](https://docs.polygon.technology/api-reference/wallet/get-current-balance-of-a-specific-wallet.md): Returns the current balance of a specific wallet, including the display balance and its estimated value in the currency requested via `estimatedBalanceCurrencyCode` (defaults to USD).
- [List wallet transactions](https://docs.polygon.technology/api-reference/wallet/list-wallet-transactions.md): Returns the transaction history for the specified wallet, most recent first, with cursor-based pagination and optional type/date filters. Each entry is a single account-ledger movement (credit, debit, hold, or release), covering both inbound and outbound activity on the wallet. Each carries a `balan…
- [List cash locations](https://docs.polygon.technology/api-reference/cashlocation/list-cash-locations.md): Returns cash pickup and deposit locations for the given provider within range of the supplied coordinates, each with its distance from that point. Use the flow parameter to select the cash-in or cash-out provider configuration.
- [Webhook events](https://docs.polygon.technology/api-reference/webhook-events.md): The catalog of webhook events OMS delivers, and the envelope every event arrives in.
- [Create a webhook](https://docs.polygon.technology/api-reference/webhooks/create-a-webhook.md): Registers an HTTPS endpoint with event subscriptions. The HMAC signing key is returned in cleartext once and never again.
- [List webhooks](https://docs.polygon.technology/api-reference/webhooks/list-webhooks.md): Returns a paginated list of webhooks registered under the current Project.
- [Get webhook by ID](https://docs.polygon.technology/api-reference/webhooks/get-webhook-by-id.md)
- [Update a webhook](https://docs.polygon.technology/api-reference/webhooks/update-a-webhook.md): Partial update of URL, subscriptions, timeout, and notify threshold. Lifecycle is managed via enable/disable.
- [Delete a webhook](https://docs.polygon.technology/api-reference/webhooks/delete-a-webhook.md): Soft delete. The webhook is hidden from List/Get but delivery history is retained for the configured retention window.
- [Enable a webhook](https://docs.polygon.technology/api-reference/webhooks/enable-a-webhook.md): Reactivates a webhook from any non-enabled state, including suspended. Resets the failure/down episode.
- [Disable a webhook](https://docs.polygon.technology/api-reference/webhooks/disable-a-webhook.md): Stops dispatch and skips the webhook's queued deliveries. Idempotent.
- [Rotate the signing key](https://docs.polygon.technology/api-reference/webhooks/rotate-the-signing-key.md): Issues a new HMAC signing key for the webhook. The cleartext key is returned once.
- [Send a test delivery](https://docs.polygon.technology/api-reference/webhooks/send-a-test-delivery.md): Synthesizes a test delivery to the registered endpoint so partners can verify signature and reachability.
- [List deliveries for a webhook](https://docs.polygon.technology/api-reference/webhooks/list-deliveries-for-a-webhook.md): Returns a paginated list of deliveries for the webhook. Attempts are not included; use get-webhook-delivery to expand a delivery with its attempts.
- [Get a delivery with its attempts](https://docs.polygon.technology/api-reference/webhooks/get-a-delivery-with-its-attempts.md)
- [Retry deliveries](https://docs.polygon.technology/api-reference/webhooks/retry-deliveries.md): Re-queues deliveries, resetting failedAttempts to zero. Provide explicit deliveryIds, or a status plus a createdAt range to retry all matching deliveries. Every retry is audited.
- [List Deposit Address transactions](https://docs.polygon.technology/api-reference/depositaddress/list-deposit-address-transactions.md): Returns the payment transactions that originated from this Deposit Address, most recent first, with cursor-based pagination. Uses the same grouped payment read model as `GET /transactions`, pinned to this deposit address (equivalent to `GET /transactions?depositAddressId=`).
- [List Virtual Account transactions](https://docs.polygon.technology/api-reference/virtualaccount/list-virtual-account-transactions.md): Returns the payment transactions that originated from this Virtual Account, most recent first, with cursor-based pagination. Uses the same grouped payment read model as `GET /transactions`, pinned to this virtual account (equivalent to `GET /transactions?virtualAccountId=`).
- [List supported networks](https://docs.polygon.technology/api-reference/reference/list-supported-networks.md): Lists every network OMS supports, with its identifiers, available assets, and which OMS resources can use it in which direction. Availability is derived from live route configuration, so a network absent from this list is not routable. Fiat-rail availability reflects the calling project's own config…
- [Simulate inbound transfer on a Virtual Account](https://docs.polygon.technology/api-reference/sandbox/simulate-inbound-transfer-on-a-virtual-account.md): Simulate an inbound fiat transfer against a Virtual Account, for testing webhook and reconciliation flows. Sandbox / non-production only; returns 404 in production-live. Set the `type` field in the request body to choose the transfer rail: `bankUs` (network `ach` or `wire`) or `bankIban` (network `s…
- [Simulate cash-in present code](https://docs.polygon.technology/api-reference/sandbox/simulate-cash-in-present-code.md): Simulate the customer presenting their cash-in code at the register (sandbox only).
- [Simulate cash-in deposit cash](https://docs.polygon.technology/api-reference/sandbox/simulate-cash-in-deposit-cash.md): Simulate the customer handing over the cash, completing the authorized deposit (sandbox only).
- [Simulate cash-in cancel](https://docs.polygon.technology/api-reference/sandbox/simulate-cash-in-cancel.md): Simulate the customer cancelling the authorization before handing over the cash (sandbox only).
- [Polygon infrastructure: Polygon Chain, CDK, Agglayer, and agentic](https://docs.polygon.technology/infrastructure/index.md): The permissionless foundation of the Open Money Stack. Polygon Chain for public settlement, Polygon CDK for private blockchains, Agglayer for cross-chain interoperability, and agentic infrastructure for autonomous AI agent payments.
- [Build with AI](https://docs.polygon.technology/resources/build-with-ai.md): AI tools and integrations for building on OMS with your IDE or coding assistant.
- [Guides](https://docs.polygon.technology/resources/guides.md): Browse guides across the Open Money Stack, filterable by product and use case.
- [Changelog](https://docs.polygon.technology/changelog.md): Product updates across the Polygon ecosystem.
- [Polygon Security Overview](https://docs.polygon.technology/tools/security/overview.md): How Polygon Labs approaches information security: team structure, monitoring, assessments, and bug bounties.
- [Governance & management](https://docs.polygon.technology/tools/security/governance.md): How Polygon Labs structures its security program using ISO/IEC 27001, including ISMS design, risk management, and policy governance.
- [Risk management](https://docs.polygon.technology/tools/security/risk.md): Polygon Labs' approach to security risk management, including risk assessment methodology, control standards, residual risk handling, and compliance mapping.
- [Human resources](https://docs.polygon.technology/tools/security/hr.md): Polygon Labs' security practices for personnel onboarding, offboarding, access provisioning, and security awareness training.
- [Infrastructure](https://docs.polygon.technology/tools/security/infrastructure.md): Security practices for Polygon network infrastructure, including onchain monitoring and multisig signer requirements.
- [Software development](https://docs.polygon.technology/tools/security/sdlc.md): Security practices applied throughout Polygon Labs' software development lifecycle, including threat modeling, CI/CD controls, and pre-production assessments.
- [Smart contracts](https://docs.polygon.technology/tools/security/smartcontracts.md): Polygon Labs' approach to smart contract security, including coding standards, internal review processes, and external audit practices.
- [Vulnerability management](https://docs.polygon.technology/tools/security/vulnerability.md): How Polygon Labs identifies, tracks, prioritizes, and remediates security vulnerabilities across its systems and applications.
- [Security operations](https://docs.polygon.technology/tools/security/operations.md): Polygon Labs' security operations practices, including logging, monitoring, incident response, and access control.
- [Security reports](https://docs.polygon.technology/tools/security/reports.md): Public security audits, penetration tests, and certifications for Polygon infrastructure and applications.
- [Bug bounty programs](https://docs.polygon.technology/tools/security/bugbounty.md): Active bug bounty programs for Polygon infrastructure, including platforms, scopes, and reward ranges.
- [Responsible disclosure](https://docs.polygon.technology/tools/security/disclosure.md): Steps for reporting a security vulnerability or CVE in Polygon technology to the security team before public disclosure.
- [Contact us](https://docs.polygon.technology/tools/security/contact.md): Contact information for the Polygon Labs security team.
- [Polygon Chain overview](https://docs.polygon.technology/pos/overview.md): Polygon Chain is an EVM-compatible blockchain anchored to Ethereum. Sub-5 second finality, 3,800 TPS, and $0.002 average transaction cost. Architecture, finality, and core contracts explained.
- [Building on PoS](https://docs.polygon.technology/pos/get-started/building-on-polygon.md): How to connect to Polygon Chain, deploy contracts, bridge tokens, and find the right tooling for your project.
- [USDC Native Integration](https://docs.polygon.technology/payment-services/stablecoins/usdc-native-integration.md): How to read balances and transfer native USDC on Polygon Chain using viem.
- [USDC Gateway Integration](https://docs.polygon.technology/payment-services/stablecoins/usdc-gateway-integration.md): How to integrate USDC on Polygon using Circle's Gateway (CCTP) for cross-chain transfers.
- [Prerequisites](https://docs.polygon.technology/pos/how-to/prerequisites.md): System requirements, port configuration, and setup checklist for running a Polygon Chain full node or validator node.
- [Sync node using snapshots](https://docs.polygon.technology/pos/how-to/snapshots.md): Steps to download and apply community snapshots to sync a Polygon Chain sentry, validator, or full node without syncing from scratch.
- [Using binaries](https://docs.polygon.technology/pos/how-to/full-node/full-node-binaries.md): Steps to install Heimdall and Bor binaries, configure, and start a Polygon Chain full node.
- [Using Docker](https://docs.polygon.technology/pos/how-to/full-node/full-node-docker.md): Steps to run a Polygon Chain full node using official Docker images, including Heimdall and Bor setup on Linux.
- [Using Ansible](https://docs.polygon.technology/pos/how-to/full-node/full-node-ansible.md): Steps to deploy and manage a Polygon Chain full node using an Ansible playbook.
- [Using packages](https://docs.polygon.technology/pos/how-to/full-node/full-node-packages.md): Steps to install Heimdall and Bor packages, configure, and start a Polygon Chain full node.
- [Using GCP](https://docs.polygon.technology/pos/how-to/full-node/full-node-gcp.md): Steps to deploy a Polygon Chain node in a Google Cloud Platform VM instance using the gcloud CLI.
- [Run an Erigon archive node](https://docs.polygon.technology/pos/how-to/erigon-archive-node.md): Steps to install, configure, and start an Erigon archive node for Polygon Chain mainnet or Amoy testnet.
- [Technical FAQs](https://docs.polygon.technology/pos/how-to/troubleshoot/technical-faqs.md): Reference answers to common technical questions about running Polygon Chain validator nodes, including key management, default directories, and troubleshooting commands.
- [Known issues and errors](https://docs.polygon.technology/pos/how-to/troubleshoot/known-issues.md): Diagnosis and resolution steps for common Bor and Heimdall errors encountered while running a Polygon Chain validator node.
- [Reporting issues](https://docs.polygon.technology/pos/how-to/troubleshoot/reporting-issues.md): Where to report bugs, security vulnerabilities, and node issues for Polygon Chain, including bug bounty programs and support channels.
- [Polygon Portal](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/portal-ui.md): Reference overview of the Polygon Portal bridge, including how tokens are locked and minted when crossing between Ethereum and Polygon Chain.
- [Ethereum to PoS](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/ethereum-to-matic.md): Deploy sender and receiver contracts to transfer arbitrary data from Ethereum to Polygon Chain using the state sync mechanism.
- [PoS to Ethereum](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/matic-to-ethereum.md): Deploy child and root contracts to transfer data from Polygon Chain back to Ethereum using checkpoints and the RootChainManager.
- [Submit mapping request](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/submit-mapping-request.md): Steps to submit a token mapping request to enable bridging between Ethereum and Polygon Chain.
- [State Transfer](https://docs.polygon.technology/pos/how-to/bridging/l1-l2-communication/state-transfer.md): Overview of L1-L2 state transfer options on Polygon Chain, including state sync, FxPortal, and the token bridge.
- [Becoming a validator](https://docs.polygon.technology/pos/get-started/becoming-a-validator.md): Requirements, responsibilities, and links to the step-by-step guides for joining and operating the Polygon Chain validator set.
- [Validator best practices](https://docs.polygon.technology/pos/how-to/validator/validator-best-practices.md): Security and operational best practices for running a Polygon Chain validator node, covering key management, OS hardening, networking, and monitoring.
- [Using binaries](https://docs.polygon.technology/pos/how-to/validator/validator-binaries.md): Steps to install Heimdall and Bor binaries, configure sentry and validator nodes, and start a Polygon Chain validator using binaries.
- [Using Ansible](https://docs.polygon.technology/pos/how-to/validator/validator-ansible.md): Steps to deploy a Polygon Chain sentry node and validator node using an Ansible playbook.
- [Using packages](https://docs.polygon.technology/pos/how-to/validator/validator-packages.md): Steps to install Heimdall and Bor packages, configure sentry and validator nodes, and start a Polygon Chain validator.
- [Next steps](https://docs.polygon.technology/pos/how-to/operate-validator-node/next-steps.md): Steps to stake tokens, set commission, claim rewards, and complete onboarding after your validator node joins the Polygon Chain active set.
- [Change owner and signer address](https://docs.polygon.technology/pos/how-to/operate-validator-node/change-signer-address.md): Steps to transfer your validator NFT to a new owner address or update the signer address for your Polygon Chain validator node.
- [Top up Heimdall fee](https://docs.polygon.technology/pos/how-to/operate-validator-node/topup-heimdall-fee.md): Steps to top up the Heimdall fee for a Polygon Chain validator using the Staking UI or Etherscan.
- [Validator performance requirements](https://docs.polygon.technology/pos/how-to/operate-validator-node/validator-performance.md): Reference for the validator performance parameters, benchmarks, grace periods, and forced unstaking process defined in PIP-4.
- [Delegate tokens](https://docs.polygon.technology/pos/how-to/delegate.md): Steps to delegate POL tokens to a validator, withdraw rewards, restake, and manage your stake on Polygon Chain.
- [Overview](https://docs.polygon.technology/pos/architecture/overview.md): Architectural overview of Polygon Chain from a node perspective, covering the Heimdall-v2 consensus layer and Bor execution layer.
- [Introduction](https://docs.polygon.technology/pos/architecture/bor/introduction.md): How Bor, Polygon Chain's block production layer, works: producer selection, spans, sprints, stall detection, and state synchronization with Ethereum.
- [State sync](https://docs.polygon.technology/pos/architecture/bor/state-sync.md): How state sync works in Polygon Chain, allowing Ethereum contract state to be reflected in Bor through the StateSender and StateReceiver contracts.
- [Network configuration](https://docs.polygon.technology/pos/architecture/bor/network-config.md): Default ports used by Bor and Heimdall nodes for peer connections, RPC, WebSocket, monitoring, and discovery.
- [Introduction](https://docs.polygon.technology/pos/architecture/heimdall_v2/introduction.md): What Heimdall-v2 is, what it does in the Polygon Chain architecture, and how it differs from the original Heimdall.
- [Changes from v1](https://docs.polygon.technology/pos/architecture/heimdall_v2/changes-from-v1.md): Key differences between Heimdall v1 and v2, including encoding changes, the keyring requirement for validator signing, and vote extensions.
- [Authentication](https://docs.polygon.technology/pos/architecture/heimdall_v2/authentication.md): How the Heimdall auth module handles account types, transaction validation, gas fees, AnteHandlers, and keepers.
- [Balance transfers](https://docs.polygon.technology/pos/architecture/heimdall_v2/balance-transfers.md): How the Heimdall bank module handles multi-asset coin transfers, module accounts, supply tracking, send restrictions, and CLI/gRPC/REST query commands.
- [Staking](https://docs.polygon.technology/pos/architecture/heimdall_v2/staking.md): How the Heimdall stake module manages validator state, synchronizes Ethereum stake events to Heimdall, and updates the validator set.
- [Checkpoints](https://docs.polygon.technology/pos/architecture/heimdall_v2/checkpoints.md): How Heimdall checkpoints work, from proposal through Ethereum submission and acknowledgment, including the ABCI++ processing flow and message types.
- [Topup](https://docs.polygon.technology/pos/architecture/heimdall_v2/topup.md): How the Heimdall topup module manages validator fee balances on Heimdall, including funding methods, bridge processing, and fee withdrawal.
- [Chain management](https://docs.polygon.technology/pos/architecture/heimdall_v2/chain-management.md): How the Heimdall chainmanager module stores and exposes PoS protocol parameters, including contract addresses, chain IDs, and confirmation block counts.
- [Governance](https://docs.polygon.technology/pos/architecture/heimdall_v2/governance.md): How the Heimdall governance module works, including proposal submission, voting, deposit handling, and parameter changes.
- [Clerk](https://docs.polygon.technology/pos/architecture/heimdall_v2/clerk.md): How the Heimdall clerk module manages state-sync event records from Ethereum, including the EventRecord structure and the validation flow.
- [Heimdall Bor module](https://docs.polygon.technology/pos/architecture/heimdall_v2/heimdall-bor-module.md): How the Heimdall bor module manages span intervals, selects block producers for the Bor chain, and coordinates span proposals through the ABCI++ side-transaction flow.
- [Milestones](https://docs.polygon.technology/pos/architecture/heimdall_v2/milestones.md): How Heimdall milestones provide deterministic finality on Polygon Chain without waiting for checkpoints, using CometBFT vote extensions and 2/3 majority agreement.
- [Governance fundamentals](https://docs.polygon.technology/pos/governance/governance-fundamentals.md): How Polygon Chain governance works, from off-chain ecosystem consensus through onchain upgrade execution.
- [Finality](https://docs.polygon.technology/pos/concepts/finality/finality.md): How finality works on Polygon Chain, including the milestone mechanism and the difference between probabilistic and deterministic finality.
- [Migrate to POL](https://docs.polygon.technology/pos/concepts/tokens/matic-to-pol.md): How to migrate MATIC tokens to POL, depending on which chain they are currently on.
- [POL](https://docs.polygon.technology/pos/concepts/tokens/pol.md): What POL is, how it works as the native token of Polygon Chain, and how its emission and governance mechanisms are designed.
- [sPOL](https://docs.polygon.technology/pos/concepts/tokens/spol.md): What sPOL is, how Polygon's liquid staking token works, and how to stake POL to receive sPOL.
- [MATIC](https://docs.polygon.technology/pos/concepts/tokens/matic.md): What MATIC was as the native token of Polygon Chain, and its relationship to the POL token that replaced it.
- [EIP-1559](https://docs.polygon.technology/pos/concepts/transactions/eip-1559.md): How EIP-1559 changed gas estimation and transaction fees on Polygon Chain, and how Type 2 transactions differ from legacy transactions.
- [EIP-4337](https://docs.polygon.technology/pos/concepts/transactions/eip-4337.md): How ERC-4337 account abstraction works on Polygon Chain, including UserOperations, Bundlers, EntryPoints, and Paymasters.
- [Meta transactions](https://docs.polygon.technology/pos/concepts/transactions/meta-transactions.md): What meta transactions are, why they matter, and how the relayer model decouples gas payment from transaction signing on Polygon Chain.
- [Genesis contracts](https://docs.polygon.technology/pos/reference/contracts/genesis-contracts.md): List of genesis contracts deployed on Polygon Chain mainnet and Amoy testnet, with contract addresses.
- [Delegation via validator shares](https://docs.polygon.technology/pos/reference/contracts/delegation.md): Contract reference for the validator share delegation mechanism on Polygon Chain.
- [Staking manager](https://docs.polygon.technology/pos/reference/contracts/stakingmanager.md): Contract reference for the StakeManager contract on Polygon Chain, covering validator management, staking, and reward distribution.
- [Rewards and staking incentives](https://docs.polygon.technology/pos/reference/rewards.md): Reference for Polygon Chain validator and delegator reward rates, staking incentives, and transaction fee distribution.
- [Setting Up Telemetry](https://docs.polygon.technology/pos/reference/telemetry-setup-guide.md): Configuration reference for setting up telemetry monitoring for Bor and Heimdall nodes.
- [Default ports for nodes](https://docs.polygon.technology/pos/reference/port-management.md): Reference for default ports used by Bor and Heimdall nodes on Polygon Chain.
- [Network upgrade process](https://docs.polygon.technology/pos/reference/network-upgrade-process.md): Reference for Polygon Chain hardfork activations, versions, and the network upgrade process.
- [Common commands](https://docs.polygon.technology/pos/reference/commands.md): Reference for common Bor and Heimdall commands used by Polygon Chain node operators.
- [Seed and bootnodes](https://docs.polygon.technology/pos/reference/seed-and-bootnodes.md): List of seed nodes and bootnodes for the Polygon Chain mainnet and Amoy testnet, for Bor and Heimdall.
- [PoS mainnet multi-signatures](https://docs.polygon.technology/pos/reference/commit-chain-multisigs.md): Reference for active multi-signature wallets on the Polygon Chain mainnet and commitchain.
- [RPC endpoints](https://docs.polygon.technology/pos/reference/rpc-endpoints.md): Network details and RPC endpoints for the Polygon Chain mainnet and Amoy testnet.
- [Mapped tokens](https://docs.polygon.technology/pos/reference/mapped-tokens.md): List of token mappings on the Polygon Chain mainnet and Amoy testnet.
- [Developer Tools for Polygon](https://docs.polygon.technology/tools/index.md): Tools, integrations, and infrastructure for building on Polygon Chain.
- [On-ramps & Off-ramps](https://docs.polygon.technology/payments/onramps-offramps.md): Convert between fiat and stablecoins via OMS or third-party providers on Polygon.
- [Payment Providers](https://docs.polygon.technology/payments/payment-providers.md): Directory of payment infrastructure projects supporting Polygon.
- [Test token faucets](https://docs.polygon.technology/tools/gas/matic-faucet.md): How to obtain test POL and ETH tokens for Polygon testnets using third-party faucets.
- [Estimate gas fees](https://docs.polygon.technology/tools/gas/polygon-gas-station.md): How to query Polygon Gas Station for gas price recommendations, and how to interpret the response.
- [Polygon Portal](https://docs.polygon.technology/tools/wallets/portal.md): How to connect a wallet, bridge tokens, claim bridged assets, and add custom tokens using Polygon Portal.
- [MetaMask on Polygon](https://docs.polygon.technology/tools/wallets/metamask/overview.md): MetaMask key properties and security tips for use with Polygon networks.
- [Add Polygon network](https://docs.polygon.technology/tools/wallets/metamask/add-polygon-network.md): How to add Polygon Chain to MetaMask using ChainList, Polygonscan, or manual entry.
- [Getting Started with Polygon Wallets](https://docs.polygon.technology/tools/wallets/getting-started.md): An overview of wallet options compatible with Polygon networks and how to choose one.
- [WalletConnect](https://docs.polygon.technology/tools/wallets/walletconnect.md): Please view the third-party content disclaimer here.
- [Reown](https://docs.polygon.technology/tools/wallets/reown.md): How to integrate Reown AppKit or WalletKit for wallet connections and Web3 UX on Polygon.
- [AppKit](https://docs.polygon.technology/tools/wallets/appkit.md): How to integrate Reown AppKit for wallet connections in a Polygon dApp.
- [WalletKit](https://docs.polygon.technology/tools/wallets/walletkit.md): Please view the third-party content disclaimer here.
- [Interact with a node RPC](https://docs.polygon.technology/tools/dApp-development/tutorials/access-node.md): How to connect to a Polygon RPC provider and send your first blockchain request using Alchemy.
- [Hardhat](https://docs.polygon.technology/tools/dApp-development/common-tools/hardhat.md): Build, test, and deploy a smart contract to Polygon Amoy using Hardhat.
- [Remix](https://docs.polygon.technology/tools/dApp-development/common-tools/remix.md): Deploy a HelloWorld smart contract to Polygon Amoy using Remix IDE and MetaMask.
- [Replit](https://docs.polygon.technology/tools/dApp-development/common-tools/replit.md): Deploy a Solidity smart contract to Polygon Amoy using Replit IDE, without any local environment setup.
- [dApp Launchpad Introduction](https://docs.polygon.technology/tools/dApp-development/launchpad/intro.md): What dApp Launchpad is, what it automates, and when to use it.
- [Quickstart](https://docs.polygon.technology/tools/dApp-development/launchpad/quickstart.md): Build and run your first dApp Launchpad project from installation to a live local development environment.
- [Frontend](https://docs.polygon.technology/tools/dApp-development/launchpad/frontend.md): How to work with the Next.js frontend in a dApp Launchpad project, including wallet connections, contract interactions, and deployment.
- [Smart contracts](https://docs.polygon.technology/tools/dApp-development/launchpad/smart-contracts.md): How to work with smart contracts in a dApp Launchpad project, including local deployment, the block explorer, and production deployment.
- [Commands](https://docs.polygon.technology/tools/dApp-development/launchpad/commands.md): Complete reference for all dApp Launchpad CLI commands and their options.
- [Contributing](https://docs.polygon.technology/tools/dApp-development/launchpad/contributing.md): How to build dApp Launchpad from source and run a local development environment for the tool itself.
- [Common pitfalls](https://docs.polygon.technology/tools/dApp-development/launchpad/common-pitfalls.md): Known issues in dApp Launchpad with their causes and solutions.
- [Tutorials](https://docs.polygon.technology/tools/dApp-development/third-party-tutorials.md): Index of third-party resources and tutorials for developing, deploying, and managing dApps on Polygon.
- [Chain Indexer Framework Overview](https://docs.polygon.technology/tools/chain-indexer-framework/overview.md): How the Chain Indexer Framework works and why it is useful for building event-driven dApp backends on EVM chains.
- [Usage](https://docs.polygon.technology/tools/chain-indexer-framework/usage.md): How to install the Chain Indexer Framework and run the provided example pipelines.
- [Get started](https://docs.polygon.technology/tools/matic-js/get-started.md): Matic.js a JavaScript library that facilitates interaction with the Polygon network. It provides developers with simplified operations such as depositing, trans
- [POS client](https://docs.polygon.technology/tools/matic-js/pos/client.md): Make sure you have set up Matic.js by following the get started guide.
- [ERC20 with Matic.js on Polygon PoS](https://docs.polygon.technology/tools/matic-js/pos/erc20/index.md): The POSClient has an erc20 method which returns an object of an ERC20 token.
- [approveMax](https://docs.polygon.technology/tools/matic-js/pos/erc20/approve-max.md): The approveMax method can be used to approve max amount on the root token.
- [approve](https://docs.polygon.technology/tools/matic-js/pos/erc20/approve.md): The approve method can be used to approve required amount on the root token.
- [deposit](https://docs.polygon.technology/tools/matic-js/pos/erc20/deposit.md): The deposit method can be used to deposit required amount from root token to child token.
- [getAllowance](https://docs.polygon.technology/tools/matic-js/pos/erc20/get-allowance.md): The getAllowance method can be used to get the approved amount for the user.
- [getBalance](https://docs.polygon.technology/tools/matic-js/pos/erc20/get-balance.md): The getBalance method can be used to get the balance of user. It is available on both child and parent token.
- [isWithdrawExited](https://docs.polygon.technology/tools/matic-js/pos/erc20/is-withdraw-exited.md): The isWithdrawExited method can be used to know whether the withdraw has been exited or not.
- [transfer](https://docs.polygon.technology/tools/matic-js/pos/erc20/transfer.md): The transfer method can be used to transfer amount from one address to another address.
- [withdrawExitFaster](https://docs.polygon.technology/tools/matic-js/pos/erc20/withdraw-exit-faster.md): The withdrawExitFaster method can be used to exit the withdraw process faster by using the txHash from withdrawStart method.
- [withdrawExit](https://docs.polygon.technology/tools/matic-js/pos/erc20/withdraw-exit.md): The withdrawExit method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawStart](https://docs.polygon.technology/tools/matic-js/pos/erc20/withdraw-start.md): The withdrawStart method can be used to initiate the withdraw process which will burn the specified amount on polygon chain.
- [ERC721 with Matic.js on Polygon PoS](https://docs.polygon.technology/tools/matic-js/pos/erc721/index.md): POSClient provides erc721 method which helps you to interact with a erc721 token.
- [approveAll](https://docs.polygon.technology/tools/matic-js/pos/erc721/approve-all.md): The approveAll method can be used to approve all tokens.
- [approve](https://docs.polygon.technology/tools/matic-js/pos/erc721/approve.md): The approve method can be used to approve required amount on root token.
- [depositMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/deposit-many.md): The depositMany method can be used to deposit multiple token from ethereum to polygon chain.
- [deposit](https://docs.polygon.technology/tools/matic-js/pos/erc721/deposit.md): The deposit method can be used to deposit a token from ethereum to polygon chain.
- [getAllTokens](https://docs.polygon.technology/tools/matic-js/pos/erc721/get-all-tokens.md): The getAllTokens method returns all tokens owned by specified user.
- [getTokenIdAtIndexForUser](https://docs.polygon.technology/tools/matic-js/pos/erc721/get-token-id-at-index-for-user.md): The getTokenIdAtIndexForUser method returns token id on supplied index for user.
- [getTokensCount](https://docs.polygon.technology/tools/matic-js/pos/erc721/get-tokens-count.md): The getTokensCount method returns tokens count for specified user.
- [isApprovedAll](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-approved-all.md): The isApprovedAll method checks if all token is approved. It returns boolean value.
- [isApproved](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-approved.md): The isApproved method checks if token is approved for specified tokenId. It returns boolean value.
- [isWithdrawExitedMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-withdraw-exited-many.md): The isWithdrawExitedMany method check if withdraw has been exited for multiple tokens. It returns boolean value.
- [isWithdrawExited](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-withdraw-exited.md): The isWithdrawExited method check if a withdraw has been exited. It returns boolean value.
- [transfer](https://docs.polygon.technology/tools/matic-js/pos/erc721/transfer.md): The transfer method can be used to transfer tokens from one user to another user.
- [withdrawExitFasterMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit-faster-many.md): The withdrawExitFasterMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawExitFaster](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit-faster.md): The withdrawExitFaster method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawExitMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit-many.md): The withdrawExitMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawExit](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit.md): withdrawExit method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawStartMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-start-many.md): The withdrawStartMany method can be used to initiate the withdraw process which will burn the multiple token on polygon chain.
- [withdrawStartWithMetaData](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-start-with-meta-data.md): The withdrawStartWithMetaData method can be used to initiate the withdraw process which will burn the specified token on polygon chain. Under the hood it calls
- [withdrawStart](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-start.md): The withdrawStart method can be used to initiate the withdraw process which will burn the specified token on polygon chain.
- [approveAllForMintable](https://docs.polygon.technology/tools/matic-js/pos/erc1155/approve-all-for-mintable.md): The approveAllForMintable method can be used to approve all mintable tokens on root token.
- [approveAll](https://docs.polygon.technology/tools/matic-js/pos/erc1155/approve-all.md): The approveAll method can be used to approve all tokens on root token.
- [depositMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/deposit-many.md): The depositMany method can be used to deposit required amounts of multiple token from ethereum to polygon chain.
- [deposit](https://docs.polygon.technology/tools/matic-js/pos/erc1155/deposit.md): The deposit method can be used to deposit required amount of a token from ethereum to polygon chain.
- [getBalance](https://docs.polygon.technology/tools/matic-js/pos/erc1155/get-balance.md): The getBalance method can be used to get the balance of user for a token. It is available on both child and parent token.
- [ERC1155 with Matic.js on Polygon PoS](https://docs.polygon.technology/tools/matic-js/pos/erc1155/index.md): POSClient provides erc1155 method which helps you to interact with a erc1155 token.
- [isApprovedAll](https://docs.polygon.technology/tools/matic-js/pos/erc1155/is-approved-all.md): The isApprovedAll method checks if all tokens are approved for a user. It returns boolean value.
- [isWithdrawExitedMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/is-withdraw-exited-many.md): The isWithdrawExitedMany method check if withdraw has been exited for multiple tokens. It returns boolean value.
- [isWithdrawExited](https://docs.polygon.technology/tools/matic-js/pos/erc1155/is-withdraw-exited.md): The isWithdrawExited method check if a withdraw has been exited. It returns boolean value.
- [transfer](https://docs.polygon.technology/tools/matic-js/pos/erc1155/transfer.md): The transfer method can be used to transfer tokens from one user to another user.
- [withdrawExitFasterMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit-faster-many.md): The withdrawExitFasterMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawExitFaster](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit-faster.md): The withdrawExitFaster method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawExitMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit-many.md): The withdrawExitMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawExit](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit.md): The withdrawExit method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawStartMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-start-many.md): The withdrawStartMany method can be used to initiate the withdraw process which will burn the specified amounts of multiple token respectively on polygon chain.
- [withdrawStart](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-start.md): The withdrawStart method can be used to initiate the withdraw process which will burn the specified amount of tokenId on polygon chain.
- [Deposit ETH](https://docs.polygon.technology/tools/matic-js/pos/deposit-ether.md): Use the depositEther method to deposit ETH from ethereum to polygon. For example:
- [isCheckPointed](https://docs.polygon.technology/tools/matic-js/pos/is-check-pointed.md): The isCheckPointed method can be used to know if a transaction has been check-pointed.
- [isDeposited](https://docs.polygon.technology/tools/matic-js/pos/is-deposited.md): The isDeposited method shows if a deposit has been completed.
- [Matic.js API Architecture](https://docs.polygon.technology/tools/matic-js/api-architecture.md): The Matic.js library follows common api architecture throughout and the APIs are divided into two types:
- [Ethers](https://docs.polygon.technology/tools/matic-js/setup/ethers.md): ethers.js is a library for interacting with the Ethereum Blockchain and its ecosystem.
- [Web3js](https://docs.polygon.technology/tools/matic-js/setup/web3js.md): Web3.js is a collection of libraries that allow you to interact with a local or remote Ethereum node using HTTP, IPC or WebSocket.
- [Set proof API](https://docs.polygon.technology/tools/matic-js/set-proof-api.md): The API links have been changed from https://apis.matic.network &amp;rarr; https://proof-generator.polygon.technology. Please make sure to update the links.
- [ABI manager](https://docs.polygon.technology/tools/matic-js/advanced/abi-manager.md): matic.js internally uses ABIManager for handling ABI management, configuration for you. All of the ABI and config are taken from static repo.
- [Exit util](https://docs.polygon.technology/tools/matic-js/advanced/exit-util.md): matic.js internally use ExitUtil for generating proofs. It is a class which has different methods for helping with exit utilities.
- [Plugin](https://docs.polygon.technology/tools/matic-js/advanced/plugin.md): Using plugin you can inject your code into matic.js. It can be used to write common set of generic codes which can be provided to anyone using a package.
- [The Graph](https://docs.polygon.technology/tools/data/thegraph.md): How to create, deploy, and query a subgraph for a Polygon smart contract using The Graph.
- [IPFS](https://docs.polygon.technology/tools/storage/ipfs.md): How to use IPFS for decentralized file storage in Polygon dApps, including example projects.
- [Filecoin](https://docs.polygon.technology/tools/storage/filecoinhelpers.md): How to use Filecoin and IPFS storage services in your Polygon dApp for persistent, decentralized file storage.
- [Crust network](https://docs.polygon.technology/tools/storage/crusthelpers.md): How to integrate Crust Network decentralized storage with your Polygon dApp using available helper tools.
- [Getting Started with Polygon Oracles](https://docs.polygon.technology/tools/oracles/getting-started.md): An explanation of blockchain oracles and how they connect smart contracts to external data on Polygon.
- [Chainlink](https://docs.polygon.technology/tools/oracles/chainlink.md): How to read a Chainlink price feed in a Solidity smart contract on Polygon.
- [Chronicle](https://docs.polygon.technology/tools/oracles/chronicle.md): How to read Chronicle oracle price data in a Solidity smart contract on Polygon zkEVM.
- [Supra](https://docs.polygon.technology/tools/oracles/supra.md): How to integrate Supra Pull Oracle and Push Oracle into a Polygon smart contract or JavaScript application.
- [Polygon CDK: private blockchains with public liquidity](https://docs.polygon.technology/chain-development/cdk/index.md): Polygon CDK lets institutions launch their own private blockchain with built-in Agglayer connectivity. Privacy as a spectrum (private validium, gated access, sovereign), 20,000+ TPS, and a bespoke chain operated with Polygon.
- [What is CDK?](https://docs.polygon.technology/chain-development/cdk/get-started/overview.md): Enterprise-grade toolkit for building custom Ethereum L2 chains. Agglayer interoperability is built in by default.
- [Why Choose CDK?](https://docs.polygon.technology/chain-development/cdk/get-started/benefits.md): Key benefits of Polygon CDK, including EVM compatibility, Agglayer integration, rollup modes, and implementation support.
- [Deployment Modes](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/architecture.md): Component reference for the three CDK deployment modes: sovereign, validium, and zkrollup.
- [Privacy Configuration](https://docs.polygon.technology/chain-development/cdk/privacy.md): Deploy a private Polygon CDK chain where transaction data stays in your infrastructure and Ethereum settles a validity proof. Built on OP Succinct AltDA.
- [Quickstart](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/local-guide.md): How to deploy a local cdk-opgeth testnet using Kurtosis, including L1, L2, Agglayer, and OP Stack components.
- [Devnet Deployment Guide](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/devnet-deployment-guide.md): How to deploy a production-like Pessimistic Proof (cdk-opgeth-sovereign) devnet.
- [Going to Production](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/going-to-production.md): Deploy a CDK chain to testnet or mainnet with support from implementation providers.
- [Integration Partner overview](https://docs.polygon.technology/chain-development/cdk/integration-partners/overview.md): What Agglayer + CDK integration means for a RaaS provider, the end-to-end journey, and what to expect from Polygon.
- [Architecture and deployment modes](https://docs.polygon.technology/chain-development/cdk/integration-partners/architecture-and-modes.md): Operator-lens component map and the four deployment modes from the Integration Partner's perspective.
- [Environments and contract addresses](https://docs.polygon.technology/chain-development/cdk/integration-partners/environments.md): Public Agglayer endpoints and contract addresses for Bali, Cardona, and Mainnet.
- [Integration flow](https://docs.polygon.technology/chain-development/cdk/integration-partners/integration-flow.md): End-to-end sequence from Jira intake to a live chain on Agglayer, with the role of each party at each step.
- [Support and resources](https://docs.polygon.technology/chain-development/cdk/integration-partners/support.md): Where to get help and reference the public tools used for Agglayer chain integration.
- [Polygon CDK FAQs](https://docs.polygon.technology/chain-development/cdk/additional-resources/faqs.md): Frequently asked questions about Polygon CDK, covering execution clients, rollup modes, and Agglayer integration.
- [Glossary](https://docs.polygon.technology/chain-development/cdk/additional-resources/glossary.md): Definitions of technical terms used throughout the Polygon CDK documentation.
- [Overview](https://docs.polygon.technology/interoperability/overview.md): Cross-chain infrastructure on Polygon: Agglayer for chain-level interoperability, Intents for application-level cross-chain execution.
- [Agglayer: secure cross-chain bridge for heterogeneous blockchains](https://docs.polygon.technology/interoperability/agglayer/index.md): Agglayer is a secure cross-chain bridge that connects the liquidity and users of heterogeneous blockchains in a single interoperability protocol. Pessimistic proofs, unified liquidity, atomic cross-chain operations. Bundled with Polygon CDK.
- [Get Started](https://docs.polygon.technology/interoperability/agglayer/get-started/index.md): Build cross-chain applications on Agglayer-connected CDK chains.
- [Supported Chains](https://docs.polygon.technology/interoperability/agglayer/supported-chains.md): Chains connected to Agglayer: chain IDs, rollup IDs, RPC endpoints, block explorers, and gas tokens.
- [Observability](https://docs.polygon.technology/interoperability/agglayer/observability.md): Prometheus metrics exposed by the Agglayer node: per-network certificate heights, error flag, and bridging-time histograms.
- [Architecture](https://docs.polygon.technology/interoperability/agglayer/core-concepts/architecture.md): Agglayer's technical architecture: the Agglayer node, Pessimistic Proof, Unified Bridge, and State Transition Proof and how they coordinate
- [What is Agglayer?](https://docs.polygon.technology/interoperability/agglayer/core-concepts/what-is-agglayer.md): CDK's interoperability layer: how it addresses blockchain fragmentation and what it enables for CDK chains
- [Architecture](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/architecture.md): AggKit's three-tier architecture: chain domain, synchronization components, and the Agglayer ecosystem, with certificate submission and GER propagation flows
- [AggchainProofGen](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/aggchain-proof-gen.md): How AggchainProofGen generates state transition proofs for chains requiring mathematical verification of internal operations beyond ECDSA signature authorization
- [AggOracle](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/aggoracle.md): How AggOracle propagates Global Exit Root updates from Ethereum L1 to L2 chains, and the v0.3.5 committee mode security improvement
- [AggSender](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/aggsender.md): How AggSender packages L2 state transitions into cryptographically signed certificates and submits them to Agglayer for Pessimistic Proof generation
- [AutoClaim](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/autoclaim.md): Optional AggKit component that discovers L1 to L2 bridge exits, prepares claim proofs, and submits claim transactions on the destination L2
- [BridgeSync](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/bridge-sync.md): How BridgeSync monitors and indexes bridge events from L1 and L2 networks, and how it provides data to AggSender and Bridge Service
- [Components Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/index.md): The 8 AggKit components, their roles, dependencies, and which combinations are appropriate for different deployment scenarios
- [L1InfoTreeSync](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/l1infotree-sync.md): How L1InfoTreeSync monitors Ethereum L1 and maintains the L1 Info Tree and Rollup Exit Tree for proof generation and certificate building
- [L2GERSync](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/l2ger-sync.md): How L2GERSync indexes Global Exit Root updates on the L2 side and provides fast local GER state access for claim verification and Bridge Service APIs
- [Architecture Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/architecture.md): How Pessimistic Proofs are generated and validated, and the financial isolation guarantees they provide
- [Benchmarks](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/benchmarks.md): Experimental performance analysis and benchmarks across different zkVM implementations
- [Data Structures](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/data-structures.md): Reference for the Sparse Merkle Trees and data structures used by Pessimistic Proof: Local Balance Tree, Nullifier Tree, Bridge Exits, MultiBatchHeader, and Certificate
- [Proof Generation](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/proof-generation.md): The Pessimistic Proof generation pipeline: certificate submission, native Rust validation, zkVM proof generation, and proof verification
- [Aggchain Proof](https://docs.polygon.technology/interoperability/agglayer/core-concepts/state-transition-proof/aggchain-proof.md): Reference for Aggchain Proof: ECDSA and generic validity proof consensus types, data structures, verification steps, and bridge constraint details
- [Architecture Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/state-transition-proof/architecture.md): The State Transition Proof dual proof system: Local Chain, AggProver, and Agglayer roles, and how ECDSA and generic consensus types are handled
- [Architecture Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/architecture.md): The Unified Bridge architecture: onchain contracts, off-chain services, data flow, and security properties
- [Asset Bridging](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/asset-bridging.md): How asset bridging works in the Unified Bridge: token type handling, bridgeAsset/claimAsset function signatures, and Merkle proof verification
- [Bridge Components](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/bridge-components.md): Reference for the Unified Bridge's onchain contracts, off-chain services, and APIs
- [Data Structures](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/data-structures.md): Reference for the Unified Bridge Merkle tree hierarchy: Local Exit Root, Rollup Exit Root, Mainnet Exit Root, Global Exit Root, and Global Index
- [Message Bridging](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/message-bridging.md): How message bridging works in the Unified Bridge: bridgeMessage/claimMessage function signatures, the IBridgeMessageReceiver interface, and execution flows
- [Integrations](https://docs.polygon.technology/interoperability/agglayer/integrations/index.md): Tools and APIs for integrating with Agglayer bridge infrastructure.
- [Bridge Hub](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/index.md): Multi-chain bridge transaction indexing, API, and auto-claim system for Agglayer integrators.
- [Architecture](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/architecture.md): Bridge Hub system architecture: consumer internals, multi-network deployment, and database design.
- [Deployment](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/deployment.md): Deploy Bridge Hub to production: Docker, Kubernetes, configuration, and troubleshooting.
- [API Reference](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/api-reference.md): Bridge Hub REST API: endpoints, parameters, and response formats for querying bridge transactions.
- [Auto-Claim Service](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/auto-claim.md): Automated bridge transaction claiming: configuration, deployment, and security.
- [AggKit Bridge Service](https://docs.polygon.technology/interoperability/agglayer/integrations/aggkit-bridge-service/index.md): REST API for bridge data, transaction status, and proof generation without running AggKit infrastructure.
- [API Reference](https://docs.polygon.technology/interoperability/agglayer/integrations/aggkit-bridge-service/api-reference.md): REST API documentation for the AggKit Bridge Service: endpoints, parameters, and response formats.
- [Exit Certificate Tool](https://docs.polygon.technology/interoperability/agglayer/integrations/exit-certificate-tool.md): Chain-operator tool for exiting Agglayer: generate and settle a final certificate that moves every L2 balance back to L1, then serve claim proofs to users.
- [Agentic Payments Introduction](https://docs.polygon.technology/payment-services/agentic-payments/agent-integration/intro.md): Conceptual overview of agentic payments and how autonomous agents transact on Polygon.
- [Agentic Payments](https://docs.polygon.technology/wallets/agentic-wallets.md): Infrastructure for AI agents that initiate, negotiate, and settle payments autonomously on Polygon.
- [ERC-8004 on Polygon](https://docs.polygon.technology/payment-services/agentic-payments/agent-integration/erc8004.md): Reference and explanation for ERC-8004: onchain Identity, Reputation, and Validation registries for autonomous agents.
- [Agentic Services](https://docs.polygon.technology/payment-services/agentic-payments/agentic-services.md): A directory of x402-enabled APIs that can be discovered and called by AI agents using pay-per-call USDC payments on Polygon.
- [Monetize an existing REST API](https://docs.polygon.technology/payment-services/agentic-payments/solutions/monetize-existing-api.md): Open a per-call revenue channel against your existing API for agent buyers. Settle in USDC on Polygon.
- [Per-inference billing for AI APIs](https://docs.polygon.technology/payment-services/agentic-payments/solutions/per-inference-billing.md): Price model inference on actual token usage with the x402 v2 upto scheme. Polygon's mainnet facilitator runs v2 today.
- [Agentic SaaS metering](https://docs.polygon.technology/payment-services/agentic-payments/solutions/saas-metering.md): Add a per-action x402 channel to a seat-priced SaaS product. Keep enterprise contracts intact; bill agent traffic by usage.
- [Treasury yield sweep](https://docs.polygon.technology/payment-services/agentic-payments/solutions/treasury-yield-sweep.md): Sweep idle USDC into Aave v3, Morpho, or ERC-4626 vaults from the CLI. Withdraw on a schedule before the next disbursement run.
- [Cross-corridor vendor payouts](https://docs.polygon.technology/payment-services/agentic-payments/solutions/cross-corridor-payouts.md): Pay vendors and contractors in their preferred chain and currency from a single USDC treasury. Bridging is one command per recipient.
- [Polymarket hedging of operational risk](https://docs.polygon.technology/payment-services/agentic-payments/solutions/polymarket-hedging.md): Take small-dollar Polymarket positions to hedge regulatory, market, or event-driven risk from the CLI.
- [Polygon Agent CLI](https://docs.polygon.technology/payment-services/agentic-payments/cli/index.md): Command-line toolkit for agents on Polygon: smart wallets, Trails for funding and swaps and yield, x402 micropayments, ERC-8004 identity, and Polymarket.
- [Setup and wallets](https://docs.polygon.technology/payment-services/agentic-payments/cli/setup-and-wallets.md): Initialize a project, create a smart wallet with spending limits, and manage wallet lifecycle.
- [Balances and funding](https://docs.polygon.technology/payment-services/agentic-payments/cli/balances-and-funding.md): Check balances across one or many chains and fund the smart wallet through the Trails widget.
- [Transfers](https://docs.polygon.technology/payment-services/agentic-payments/cli/transfers.md): Send native tokens or ERC-20s from the smart wallet. Dry-run by default; broadcast with --broadcast.
- [Swaps and yield](https://docs.polygon.technology/payment-services/agentic-payments/cli/swaps-and-yield.md): DEX swaps, cross-chain bridging, and Trails earn pools (Aave v3, Morpho, ERC-4626), all under the smart wallet.
- [Pay an x402 endpoint](https://docs.polygon.technology/payment-services/agentic-payments/cli/x402-pay.md): Call an x402-protected resource from the CLI. The 402 is auto-paid and the request is retried as part of the same call.
- [ERC-8004 agent identity](https://docs.polygon.technology/payment-services/agentic-payments/cli/agent-identity.md): Register an onchain agent identity and manage reputation through the ERC-8004 registries on Polygon mainnet.
- [Polymarket trading](https://docs.polygon.technology/payment-services/agentic-payments/cli/polymarket.md): Trade Polymarket prediction markets from the CLI: list markets, buy and sell YES/NO tokens via CLOB, manage positions.
- [x402 protocol: agentic payments over HTTP](https://docs.polygon.technology/payment-services/agentic-payments/x402/intro.md): x402 is the open payment protocol that brings onchain payments to the HTTP 402 Payment Required status code. Build agentic and AI agent payments for APIs and web services. Polygon-supported networks, facilitators, and quickstart.
- [x402 How It Works](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/how-it-works.md): How the x402 v2 protocol turns an HTTP 402 response into a verified onchain payment, with one round-trip and no signup.
- [x402 Quickstart for Buyers](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/quickstart-buyers.md): Tutorial: set up an x402 v2 buyer client on Polygon to automatically pay for and access paywalled API endpoints.
- [x402 Quickstart for Sellers](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/quickstart-sellers.md): Tutorial: protect API endpoints with x402 v2 payment middleware to accept USDC payments on Polygon.
- [Migration: x402 V1 to V2](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/migration-v1-to-v2.md): Guide for upgrading Polygon x402 integrations from V1 to V2: packages, headers, network identifiers, and middleware patterns.
- [Facilitator Addresses](https://docs.polygon.technology/payment-services/agentic-payments/x402/analytics.md): Reference list of x402 Polygon mainnet and Amoy facilitator addresses for analytics and payment verification.

## OpenAPI Specs

- [openapi](https://docs.polygon.technology/api-reference/openapi.yaml)