Codex ACTION
Filter Tokens
Discovers and ranks tokens by on-chain signals such as volume, trending score, liquidity, or market cap. Use this to find trending tokens, top movers, or tokens matching a search phrase. To look up a specific token by its known contract address, use Get Token Details instead. Filter to a specific network by passing a numeric
networkId (e.g., 1 for Ethereum, 137 for Polygon). Use Get Networks to find numeric network IDs. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Codex account once, then configure and run Filter Tokens from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "codex-filter-tokens",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
codex: { authProvisionId: "apn_xxxxxxx" },
phrase: "Search Phrase",
networkId: 10,
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "codex-filter-tokens",
"configured_props": {
"codex": { "authProvisionId": "apn_xxxxxxx" },
"phrase": "Search Phrase",
"networkId": 10
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "codex",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "codex-filter-tokens",
arguments: {
phrase: "Search Phrase",
networkId: 10,
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
phrase Search Phrase | string | Search tokens by name or symbol (e.g., PEPE, Uniswap). Leave blank to browse by ranking. Optional |
networkId Network ID | integer | Filter results to a single blockchain network. Example: 1 for Ethereum, 137 for Polygon. Leave blank for all networks. Use Get Networks to find IDs. Optional |
sortBy Sort By | string | Ranking signal to sort results by. Optional |
limit Limit | integer | Maximum number of results to return. Optional |
offset Offset | integer | Number of results to skip for pagination. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- codex-filter-tokens
- Version
- 0.0.2
- App
- Codex
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗