Back to Browse
Beggar Bot JUP Holdings Lookup (Base Mainnet)
x402
Beggar Bot JUP Holdings Lookup (Base Mainnet) is a paid API for AI agents from beggar-bot-demand.beggarbot.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-04).
Fetches Jupiter (JUP) token holdings for a given Base58 wallet address on Base mainnet, returning up to a configurable number of rows
Price / call$0.02
Success—
StatusUnknown
How this service works
Paid: /v1/verify, /v1/risk, /v1/receipt cost $0.01 USDC per call on Base mainnet via x402 (payTo 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7); utilities analyze Base mainnet (USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) by default, network=base-sepolia optional; /v1/receipt/verify and discovery files are free. Operator: Beggar Bot.
Output
Returns a JSON array of JUP (Jupiter) token holding records for the specified Base58 wallet address on Base mainnet, with up to the specified number of rows (default 50). Each record likely includes token amounts, positions, or related holding metadata.
Example use cases
Portfolio check for a DeFi wallet
“Look up all the JUP holdings for the Base wallet address 0xDeF456... and show me up to 50 rows so I can see what they're holding.”
Whale research on JUP token
“I want to see how much JUP this Base mainnet wallet 0x789Ghi... is holding — pull the top 50 records for me.”
Agent monitoring JUP concentration
“Fetch the JUP token holdings for Base address 0xJkl012... and limit it to 20 rows so I can track this wallet's position.”
Technical details
Endpoint
GEThttps://beggar-bot-demand.beggarbot.workers.dev/v1/jupholdings?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to look up JUP (Jupiter) token holdings specifically on Base mainnet for a given wallet address. It is part of the Beggar Bot suite and uses x402 micropayment protocol at $0.02 USDC per call, making it suitable for on-demand agent queries rather than bulk analytics pipelines.
Side effects
- Invalid or malformed Base58 wallet address returns an error
- Missing required wallet query parameter returns a 400-level error
- Payment not provided or insufficient USDC results in a 402 Payment Required response
- Network connectivity issues to Base mainnet data sources may cause timeouts
- Wallet with no JUP holdings returns an empty result set
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json"
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"