List Particle Data Platform REST and MCP services

[marcel]

Motivation

Particle exposes podcast, people, and company intelligence through its own REST API and MCP server. Agents can search shows and episode dialogue, retrieve transcripts, discover guests and advertisers, and follow relationships across a connected knowledge graph. Both surfaces accept native MPP evm/charge payments in USDC on Base without an account or prepaid credits.

• Service names: Particle Data Platform; Particle Data Platform MCP
• Live service URLs: https://api.particle.pro; https://mcp.particle.pro/mcp
• Provider URL: https://particle.pro
• OpenAPI URLs: https://api.particle.pro/openapi.json; https://mcp.particle.pro/openapi.json
• Payment documentation: https://docs.particle.pro/mpp

Summary

Adds entries for all 104 paid REST endpoints and the MCP endpoint. REST prices are copied from the public OpenAPI document in atomic USDC units. MCP pricing is the sum of the billable tool calls in a request; initialization and tool discovery are free. Each entry links to its own live OpenAPI document, agent guidance, and documentation.

The catalog import needs an explicit intermediate unknown assertion because TypeScript infers optional undefined keys across the generated JSON's heterogeneous payment-method maps when evm joins tempo and stripe. The schema tests validate the generated catalog; this adjustment leaves runtime behavior unchanged.

• The service is live and accepts MPP payments.
• This PR adds its entries in schemas/services.ts.
• Listed endpoints, prices, and payment methods match the live service.
• Public documentation and icon URLs are stable and accessible.
• pnpm generate:discovery succeeds.
• pnpm check:types passes.
• pnpm build succeeds (Node 25 with --no-experimental-webstorage).
• pnpm check:ci passes.
• Catalog/schema/generator and services API tests pass: 10,009 tests across five files.

Key design considerations

• Integration: first-party; submitted on behalf of the service operator.
• Payment methods and intents: evm, charge; USDC on Base mainnet, chain ID 8453; currency 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, six decimals. x402 remains available alongside MPP.
• Provider relationship: Particle operates both public origins directly.
• Directory fit: Original podcast and entity intelligence, with separate REST and MCP discovery documents and per-operation pricing.

Production verification on 2026-09-12:

• Both public OpenAPI documents pass the official mppx/discovery validator.
• All 104 paid REST endpoints return native MPP and x402 challenges with prices matching their published offers.
• Native mppx REST and MCP calls each settled 0.01 USDC on Base, returned HTTP 200 and Payment-Receipt, and did not fall back to x402.
• Successful on-chain transfers: REST, MCP.
• Reusing the settled authorization returns HTTP 402. API-key authentication and free MCP initialization still work.

[vercel]

@marcel is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thanks for submitting a service to the MPP directory!

Complete the service pull request template in your PR description before review. It contains the current submission requirements and review criteria.

Service submission guide

[github-actions]

🔀 Changed Services

✅ Added

• particle
• particle-mcp

[marcel]

Replying to the submission checks:

• Service template guidance: the PR description follows the service template and includes both public origins, their endpoints, prices, ownership relationship, completed validation, and real Base payment evidence. The entries are in commit 1bf39ffce05b84d27cf4f0c895d66f94d847506a; no additional code change is needed.
• Changed-services report: confirmed that particle and particle-mcp are the two intended additions in 1bf39ffce05b84d27cf4f0c895d66f94d847506a. No correction is needed.
• Vercel authorization: this requires authorization from a Tempo team member. I cannot grant that team permission, so I am leaving the preview configuration unchanged. The production build, type check, lint, and 10,009 catalog/API tests passed locally for 1bf39ffce05b84d27cf4f0c895d66f94d847506a.