Particle Pro
Real-time news, company, and podcast intelligence APIs for developers — every story, every public company, and every episode, structured and ready to query.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"type": "https://docs.particle.pro/errors/payment_required",
"title": "Payment Required",
"detail": "This request costs $0.03 in USDC. Pay with x402 using PAYMENT-REQUIRED, or MPP using the WWW-Authenticate Payment challenge, or authenticate with a pp_ API key.",
"status": 402,
"resolve": {
"url": "https://docs.particle.pro/x402",
"action": "pay_per_request",
"message": "Retry with one payment: x402 PAYMENT-SIGNATURE or MPP Authorization: Payment. You can also use an API key."
},
"error_code": "payment_required"
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.03 USDC on Base to 0x59f3…1c5f7. The signed payment is good for 5 minutes.
- Paid to
- 0x59f3…1c5f7
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 30000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x59f3a6dcb6f482c53872dd8f8f9e1f9161a1c5f7",
"amount": "30000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"since": "2024-01-01",
"until": "2024-06-01",
"language": "fr"
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"type": "object",
"properties": {
"role": {
"enum": [
"guest",
"host",
"panelist",
"correspondent",
"speaker",
"mention"
],
"type": "string",
"description": "How the entity must relate to the episode. Speaking roles: 'guest', 'host', 'panelist', 'correspondent', or 'speaker' for any of them. 'mention' means the entity is talked about rather than speaking. Omit to match both. Matches the role values on /v1/podcasts/episodes."
},
"sort": {
"enum": [
"relevance",
"recency"
],
"type": "string",
"description": "Sort order. Defaults to relevance."
},
"type": {
"enum": [
"INTRO",
"PERSONAL_BANTER",
"TOPIC_DISCUSSION",
"INTERVIEW",
"TRANSITION",
"AD",
"OUTRO"
],
"type": "string",
"description": "Segment type filter."
},
"limit": {
"type": "integer",
"format": "int64",
"description": "Results per page (1-100, default 25)."
},
"since": {
"type": "string",
"description": "Only segments from episodes published after this date."
},
"until": {
"type": "string",
"description": "Only segments from episodes published on or before this date. A bare date includes that whole day."
},
"cursor": {
"type": "string",
"description": "Opaque cursor from a previous response."
},
"context": {
"type": "integer",
"format": "int64",
"description": "Lines of surrounding dialogue around each matched line (1-15, default 1). Widens each match's transcript window in place — request more context instead of fetching the full transcript. Window size stays bounded even at the maximum."
},
"language": {
"type": "string",
"description": "Restrict to episodes of podcasts in this language (ISO 639-1 code, e.g. 'fr'). Matches the podcast's primary language subtag, so 'fr' covers 'fr-FR'."
},
"entity_id": {
"type": "string",
"description": "Optional entity slug or ID. Filters results to episodes featuring this entity. For 'every line about X', use /v1/podcasts/mentions instead."
},
"company_id": {
"type": "string",
"description": "Optional company slug, domain, or ID. Resolves to the company's linked entity and applies as a filter."
},
"episode_id": {
"type": "string",
"description": "Filter to a specific episode by slug or ID."
},
"podcast_id": {
"type": "string",
"description": "Podcast slug, internal ID, or numeric iTunes ID."
},
"entity_type": {
"type": "string",
"description": "Optional entity category slug. Filters to episodes that *mention* any entity in that category (e.g. 'company', 'school', 'book'). Speakers are always people, so this filter only narrows mentioned entities. Cannot be combined with 'role'. Ignored when entity_id resolves to a specific entity. See GET /v1/entities/types for the available slugs."
},
"keyword_match": {
"enum": [
"required",
"ranked"
],
"type": "string",
"description": "How unquoted keyword_search terms are applied. 'required' (default) filters to segments containing every term, so results are guaranteed to contain what you typed — this also constrains semantic_search, making a hybrid query an intersection of the two. 'ranked' instead lets unquoted terms only boost BM25 relevance without excluding anything, which widens recall for loose bag-of-words queries but returns segments that may contain none of them. Quoted phrases are unaffected: they filter in BOTH modes, so to relax a phrase remove its quotes. Ignored when keyword_search is empty."
},
"keyword_search": {
"type": "string",
"description": "BM25 lexical search over dialogue. Use when an exact token must appear verbatim — tickers, drug names, product codes. By default every token must appear somewhere in the matched segment (see keyword_match). Wrap any token sequence in double quotes (e.g. \"machine learning\") to additionally require those words adjacent and in order in the segment's spoken dialogue — a speaker's own name is not indexed as dialogue, so quoting a person's name finds segments where the name appears in what was said, not segments they speak in. Adjacency spans consecutive lines, so a phrase may rarely straddle a line break. Multiple quoted phrases AND together (e.g. \"central bank\" \"interest rates\"). There is no boolean OR — a bare OR is treated as an ordinary word, so pass alternatives as separate requests."
},
"semantic_search": {
"type": "string",
"description": "Vector-similarity search by meaning. Express the query the way you'd describe the topic to a colleague — paraphrase tolerant, finds segments that express the same idea in different vocabulary. Combine with keyword_search for hybrid ranking. Describe a topic, not a name: to find a specific person or company, filter with entity_id / company_id (or use /v1/podcasts/mentions for every line about them) — and for an exact token like a ticker, use keyword_search."
}
}
}
},
"additionalProperties": false
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-09-20 01:02Z
- Last indexed by Roundhouse
- 2026-09-24 07:40Z
- Last enriched (probe, favicon, geo)
- 2026-09-24 07:15Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 15 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Particle Pro and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Particle%20Pro' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.particle.pro/v1/podcasts/episodes/search, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.