Discover and filter available x402 payment-gated API endpoints from the t54.ai registry. Search by name or URL, filter by status (active/inactive), data source (Coinbase Bazaar or x402scan community), and payment address presence. Results include security risk levels, validation timestamps, and overall reliability scores to help you select trustworthy endpoints for your workflows. | Input: Optional filters: search query (name/URL), status (active/inactive/unknown), source (bazaar/x402scan), payment address presence, sorting field (score/date/name), sort direction, and pagination (page number and size up to 100 items) | Output: Returns paginated list of x402 resources with: endpoint name and URL, overall reliability score, risk level, payment address, creation/validation timestamps, data source, and server status | Use cases: I need to find all active x402 endpoints that accept payments; Show me the highest-scoring payment-gated APIs from the official Bazaar registry; Search for x402 resources by name and filter by validation status; Get a list of community-discovered x402 endpoints sorted by creation date
This action will execute the specified operation when your workflow runs.
This integration requires a connector to be configured before it can be used in workflows.
Filter by payment address presence: true (has address) or false (no address)
Sort field: 'overall_score', 'created_at', 'last_validated', or 'name'
overall_scorecreated_atlast_validatednameSort direction: 'asc' or 'desc'
ascdescPage number (default: 1)
Items per page (default: 50, max: 100)
Search query for name or URL (case-insensitive partial match)
Filter by data source: 'bazaar' (official Coinbase registry) or 'x402scan' (community scanner)
bazaarx402scanFilter by server status
activeinactiveunknownPayment details from x402 facilitator
Fields
amountPaidAmount paid in smallest token unitassetToken address used for paymentnetworkNetwork where payment was made (e.g., 'base')payerPayer wallet addresstransactionTransaction hash (may be null if server doesn't return x-payment-response header)The endpoint response data. Access fields with {{nodeId.result.resource.fieldName}}
Whether the request succeeded
HTTP status code