treg_instagram_search_users $0.00235 per call
instagram.search.users — routed: best of 4 providers, own keys first. Search Instagram accounts by keyword — profile rows in `users`, from account bios and from creator directory pages (with the passage that names each account); `raw` holds the provider's full answer (Multi-provider (routed) · Instagram)
For AI agents: call treg_instagram_search_users
POST https://toll402.dev/v1/p/treg.instagram.search.users
{
"q": "…"
}Answers 402 with x402 payment requirements; pay with any x402 client (@x402/fetch, x402 for Python, toll402-client, toll402-mcp) or send a prepaid-credits key as x-toll402-key (https://toll402.dev/credits). Paid per call via x402 (USDC on Base) or with a prepaid-credits key (x-toll402-key, card at /credits); charged only on success. Start at /llms.txt or connect the MCP server:
npx -y toll402-mcp · remote https://toll402.dev/mcp.Input schema
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "identity; words an account's name or bio would carry: a topic, niche or place ('specialty coffee roaster Melbourne'); for people described by role or audience, treg.people.search's q answers better. Rows from directory pages carry no follow"
}
},
"additionalProperties": true,
"description": "Send what you know; treg sends each provider only the fields it accepts ({q}). On a miss it tries the next provider, cheapest first. Options are X-Treg-Route-* headers, never body fields. The answer is {output, raw, _treg}; X-Treg-Served-By names the provider."
}
MCP
{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}