Return the metadata an EOA wallet (Documentation Index
Fetch the complete documentation index at: https://docs-t.aionmarket.com/llms.txt
Use this file to discover all available pages before exploring further.
signatureType=0) needs in order to authorize platform fee collection on Polygon.
Overview
Before the platform can charge a Polymarket trading fee from an EOA wallet, the EOA must call:<spender> address (the platform Fireblocks Vault) plus the matching token / fee-receiver / chain metadata so callers do not have to hard-code anything.
The returned spender is the Fireblocks Vault Polygon address, not the platform fee receiver — the Vault acts as msg.sender for the eventual pUSD.transferFrom(eoa, platformFeeAddress, amount) call.
Request
No body, no query params. Authenticated with the standardAuthorization: Bearer <API_KEY> header.
Response
| Field | Type | Description |
|---|---|---|
spender | string | Platform Fireblocks Vault Polygon address. Use this as the spender argument to pUSD.approve(...). |
platformFeeAddress | string | Final fee-receiving address (0xeA44cAF1f893729342dC5D8903F658E8D3e2379B). Informational; do not approve this address. |
tokenAddress | string | pUSD ERC-20 contract address on Polygon. |
decimals | number | Token decimals (always 6 for pUSD). |
chainId | number | EVM chain ID (always 137 for Polygon mainnet). |
Examples
- curl
- Python SDK
Error Responses
| Status | Description |
|---|---|
| 400 | 无法解析 Fireblocks Vault (...) 的 Polygon 地址 — operator-side Fireblocks misconfiguration |
| 500 | Fireblocks SDK call failed |
Notes
- The
spendermay rotate if the platform changes its Fireblocks Vault. Always call this endpoint at agent startup (or before re-approving) instead of caching the address forever. - Approving with
MAX_UINT256(the SDK default) is recommended — a single approve covers all future trades at the 1% fee rate.