Plug API Documentation

Pass any EVM address and get back everything: token balances, protocol positions, onchain activity, time-series history, and chain metadata. All indexed, all normalized, all in one place. When you're ready to act on it, the same API compiles your constraints into signed-ready calldata.

Every endpoint is open. No API keys, no auth, no rate limits. Responses come back as JSON, or set the Accept header to text/event-stream for a persistent connection that pushes state as it changes onchain. Each request sample has a Prompt tab you can copy straight into an agent.

Get Address

Pass any EVM address and get back token balances across every supported chain, a portfolio valuation, and signal-level metadata. Fresh wallet or five-year accumulator, contract or EOA. The response tells you what you're looking at.

Get Positions

Balances only account for what's sitting in the wallet. Most of the capital is deployed. Lending collateral on Aave, liquidity in Uniswap pools, yield in vaults. The positions endpoint returns all of it, across every protocol, including non-tokenized positions that don't show up in a standard balance query.

Get Activity

Paginated transaction history for the address, sorted by block number descending. Swaps, transfers, deposits, mints. Each entry is typed and includes the counterparties and amounts. You can filter by type and paginate through the full history.

Get Series

OHLC price data, historical balance values, and portfolio value over configurable time ranges. Pick a resolution and a window. The response gives you the data points to build a chart, calculate P&L, or track how individual tokens in the portfolio have moved.

Get Chains

Returns the list of supported networks with their configuration and metadata. If you're building a multi-chain integration, check here first to see what's available.

Get Context

The read side of the API gives you data. The context endpoint bridges into the write side. It returns the full set of tokens, protocols, chains, and valid input ranges that the transaction compiler accepts for a given address. You call this to find out what you can do before you try to do it.

Get Transactions

Lists saved Plug transactions for the address. Filter by status, review what's been compiled, check on pending submissions. Use this to look at existing transaction records, not to create new ones.

Create Transaction

Pass structured inputs and the API compiles them into calldata ready for signing. You don't deal with ABI encoding or gas estimation. The response contains everything needed to submit the transaction to the network.