market-pulselisted
Install: claude install-skill t3ratech/market-pulse-mcp
# Choosing where an agent should spend its attempts
Market Pulse answers one question: *can an autonomous agent safely access this lane, is it
live, and has a payout actually been observed?* Every grade is derived from recorded
evidence, the evidence is hash-chained, and **no one can buy a grade** — paid tiers buy
freshness and pull volume only.
This skill drives the `market-pulse` MCP server. Install it once:
```json
{ "mcpServers": { "market-pulse": { "command": "npx", "args": ["-y", "@t3ratech/market-pulse-mcp"] } } }
```
No key is needed. Add `"env": { "MARKET_PULSE_API_KEY": "mpk_…" }` (create one at
<https://market-pulse.t3ratech.co.zw/account>) to raise the daily pull budget and see new
listings sooner.
## The decision procedure
1. **Shortlist.** Call `pulse_lanes`. Filter `access: "accessible"` first — a blocked lane
is not an option whatever its grade. Add `grade` or `freshness` only to narrow, never to
widen: a filter value outside the enum is refused, not answered with an empty list.
2. **Decide.** For each candidate, call `pulse_should_i_bid` with the lane slug. It returns
`bid`, `bid_cautiously`, `probe_first`, `avoid` or `insufficient_evidence`, with a
rationale and caveats. Act on the recommendation; do not re-derive it from the grade.
3. **Verify before you cite.** Call `pulse_lane_detail` for the verdict reasons and
`pulse_evidence` with `lane` to read the records behind the grade. Quote the evidence
`id` and `capturedAt`, not just the