# Polex-Bot > Polex-Bot lets AI agents connect a dedicated Polymarket wallet, read the account, validate and configure supported strategies, start and stop an existing trading engine, and inspect state, positions, trades, and logs. It does not provide arbitrary buy, sell, market-making, or direct order-placement endpoints. ## Agent resources - [MCP server, autonomous wallet login, and sandbox](https://www.polex-bot.xyz/agents/mcp): official MCP package with read-only defaults, supervised controls, and explicit fully autonomous private-key login/start. - [Machine-readable integration guide](https://www.polex-bot.xyz/agents.md): autonomous and bearer-token setup, tools, sandbox, and control policy. - [OpenAPI 3.1 specification](https://www.polex-bot.xyz/openapi.json): API paths, wallet connection, configuration fields, and response schemas. - [Complete agent guide](https://www.polex-bot.xyz/agents): human-readable quickstart, Node/Python/cURL examples, and safety rules. - [OAuth protected-resource metadata](https://www.polex-bot.xyz/.well-known/oauth-protected-resource): bearer-token discovery metadata. - [Integration package v1.2.0](https://www.polex-bot.xyz/downloads/polex-bot-agent-integration-1.2.0.tgz): MCP server and reference agents. ## Autonomous operating flow - Start the MCP server with `POLEX_BOT_AUTONOMOUS=true`; no initial bearer or approval token is needed. - Call `connect_wallet` with a dedicated wallet `privateKey`; `developerAddress` is optional because the tool can derive it. The key and returned token are never included in the tool result. - Call `check_readiness` and `preview_config`; apply valid settings with the unchanged `previewHash`. - Make an empty-patch preview and call `start_bot` with its fresh hash. Autonomous apply/start need no separate approval token. - Confirm actual activity through state, trades, and logs. Stop does not sell positions. ## Direct EOA mode without the Polymarket website - Use this only when the private key's EOA already holds pUSD on Polygon. Keep POL for any approval gas. Never use test/example keys in live mode. - Call `connect_wallet` with `privateKey` and `walletMode:"eoa"`; do not send `developerAddress`. The EOA is maker, signer, and funder with signature type 0. - Call `prepare_eoa_wallet` with `approve:false` to inspect collateral, gas, allowance, and the exact capped approval without broadcasting. - If needed, explicitly call it with `approve:true` to send a capped pUSD approval to Exchange V2 and wait for confirmation. `amountUsd` defaults to configured bankroll. Supervised mode also requires `approvalToken` for the transaction. - Continue only when `check_readiness` returns `ready:true`. Start fails closed without pUSD or allowance. No website, wrapping, swapping, arbitrary orders, or ERC-1155 sell approvals are provided. - Simulate the whole flow with `node examples/autonomous-agent.mjs --sandbox --eoa`; no network or transaction is used. ## Supervised operating rules - Begin read-only: account, balance, wallet readiness, configuration, and engine state. - Bearer-token mode uses `POLEX_BOT_TOKEN`; live supervised controls also require `POLEX_BOT_ENABLE_CONTROLS=true` and `POLEX_BOT_APPROVAL_TOKEN`. - Call `preview_config` before applying or starting. Show the owner the exact diff and use the returned `previewHash` and owner approval token. - Use a dedicated limited-funds wallet and one active engine per wallet. Protect private keys, tokens, and MCP tool-argument logs. - Many API failures are HTTP 200 with `ok=false`. Always inspect `ok`, `ready`, `stale`, `running`, `link`, and restrictions.