MPP Quickstart

Use the Stock Trends API with MPP

Machine Payment Protocol (MPP) is the funded session-based payment rail for the Stock Trends API.

Instead of settling each request independently on-chain, agents operate against a funded session balance using repeated premium calls.

MPP is optimized for AI-agent workflows, portfolio automation, financial research systems, and recurring premium intelligence execution.

Open API docs Back to docs x402 quickstart

MPP vs x402

MPP

Best for repeated agent workflows

  • Fund a session once
  • Use repeated premium requests
  • Lower friction than repeated on-chain settlement
  • Budgeted automation and portfolio workflows
x402

Best for permissionless pay-per-request usage

  • No funded session required
  • Per-request settlement
  • Event-driven execution
  • Standard x402 V2 — no Stock Trends-specific buyer integration

MPP consumes STC from an active funded session and does not use the x402 challenge flow. The two rails are alternatives, not layers.

Recommended MPP workflow

  1. Discover workflows using GET /v1/ai/tools
  2. Inspect live pricing using GET /v1/pricing/catalog
  3. Create or receive a funded MPP session
  4. Store the provided channel_id
  5. Execute repeated premium requests
  6. Monitor economics and usage via agent ledger endpoints

Pricing clarity: STC and USD cost

Stock Trends Credits (STC) are the API pricing unit.

Current billing presentation: 1 STC = $1.00 USD

The conversion below is illustrative, not a price list — it shows how an STC price maps to USD, using example amounts.

Example endpoint price Current USD cost
0.15 STC $0.15 USD
0.50 STC $0.50 USD
1.25 STC $1.25 USD

For the actual cost of a specific endpoint, call GET /v1/pricing/catalog. It and the API response headers remain authoritative, and endpoint costs should not be hard-coded.

Recommended first premium endpoint

GET https://api.stocktrends.com/v1/agent/screener/top

Returns top-ranked instruments filtered by trend, RSI, exchange, and ST-IM intelligence.

Access: Subscription · x402 · MPP. Call GET /v1/pricing/catalog for this endpoint's current cost before executing it.

Required MPP headers

Confirm the current header names against the applicable API documentation before building an MPP integration.

Header Example Description
X-StockTrends-Payment-Method mpp Payment rail identifier
X-StockTrends-Payment-Network base Network context
X-StockTrends-Payment-Reference mpp-ref-12345 Unique request reference
X-StockTrends-Payment-Amount 0.5 Presented request amount in STC
X-StockTrends-Payment-Channel-Id mppch_... Funded MPP session identifier

Optional agent identity headers

X-StockTrends-Agent-Id: your-agent-id
X-StockTrends-Agent-Type: autonomous
X-StockTrends-Agent-Vendor: your-vendor
X-StockTrends-Request-Purpose: screening

Example MPP request

curl "https://api.stocktrends.com/v1/agent/screener/top" \
  -H "X-StockTrends-Agent-Id: your-agent-id" \
  -H "X-StockTrends-Payment-Method: mpp" \
  -H "X-StockTrends-Payment-Network: base" \
  -H "X-StockTrends-Payment-Reference: mpp-ref-12345" \
  -H "X-StockTrends-Payment-Amount: 0.5" \
  -H "X-StockTrends-Payment-Channel-Id: mppch_..."

The API authorizes the request against the funded session, serves the premium response, and updates the session balance.

Who MPP is for

  • Repeated premium AI-agent workflows
  • Portfolio automation systems
  • Financial intelligence research pipelines
  • Budgeted recurring API execution
  • Lower-friction premium automation

Next steps

  • Use standard x402 V2 for permissionless pay-per-request execution
  • Use the Stock Trends MCP server inside MCP-compatible agent environments — note that the MCP adapter does not carry MPP sessions
  • Add ST-IM intelligence to portfolio workflows
  • Combine regime, breadth, and leadership intelligence
Open API docs x402 quickstart Connect with MCP Back to docs