Add mpp.directory skill

README.md

@@ -27,6 +27,7 @@ Bankr Skills equip builders with plug-and-play tools to build more powerful agen
 | [Quicknode](https://www.quicknode.com) | [quicknode](quicknode/) | Blockchain RPC and data access for all supported chains. Native/token balances, gas estimation, transaction status, and onchain queries for Base, Ethereum, Polygon, Solana, and Unichain. Supports API key and x402 pay-per-request access. |
 | [Hydrex](https://hydrex.fi) | [hydrex](hydrex/) | Liquidity pools on Base. Lock HYDX for voting power, vote on pool strategies, deposit single-sided liquidity into auto-managed vaults, and claim oHYDX rewards. |
 | [Helixa](https://helixa.xyz) | [helixa](helixa/) | Onchain identity and reputation for AI agents on Base. Mint identity NFTs, check Cred Scores, verify social accounts, update traits/narrative, and query the agent directory. Supports SIWA auth and x402 micropayments. |
+| [mpp.directory](https://mpp.directory) | [mpp-directory](mpp-directory/) | Public registry and routing surface for machine-payments services. Discover providers, services, endpoints, namespaces, certifications, incidents, pricing, and live signals across MPP, x402, l402, MCP, and A2A. |
 | [Polygon](https://polygon.technology) | [trails](trails/) | Cross-chain swap, bridge, and DeFi orchestration via Sequence. Swap tokens across chains, bridge assets, fund a Bankr wallet from any chain, deposit into yield vaults (Aave, Morpho), get token prices, and discover earn pools. Integrates with Bankr submit() for on-chain execution. |
 | [0xWork](https://0xwork.org) | [0xwork](0xwork/) | Decentralized task marketplace on Base. AI agents discover, claim, and complete tasks paid in USDC with on-chain escrow. Supports services, products, and reputation. |
 | [BOTCOIN](https://botcoin.money) | [BOTCOIN](BOTCOIN/) | Mine BOTCOIN by solving AI-powered hybrid challenges on Base. Stake-gated V2 mining with on-chain reward claims via Bankr. |

mpp-directory/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: mpp-directory
+description: mpp.directory is a public registry and routing surface for machine-payments services across MPP, x402, l402, MCP, and A2A. Use when an agent needs to discover providers, services, endpoints, namespaces, certifications, passports, health, pricing, incidents, or live signals before choosing an API or workflow. Triggers on mentions of mpp.directory, MPP registry, paid API discovery, endpoint routing, namespace manifests, protocol comparison, or finding the best machine-payments endpoint.
+metadata:
+  {"clawdbot":{"emoji":"📡","homepage":"https://mpp.directory"}}
+---
+
+# mpp.directory
+
+mpp.directory is a public discovery and intelligence layer for machine-payments services. It indexes providers, services, endpoints, verification state, workflow health, pricing hints, incidents, certifications, and agent-facing interfaces across multiple protocol families.
+
+## Public Surfaces
+
+- Dashboard: https://mpp.directory/v1
+- Endpoint catalog: https://mpp.directory/v1/public/endpoints
+- Services: https://mpp.directory/v1/services
+- Providers: https://mpp.directory/v1/providers
+- Signals: https://mpp.directory/v1/signals
+- Router UI: https://mpp.directory/v1/router
+- Compare UI: https://mpp.directory/v1/compare
+- Market UI: https://mpp.directory/v1/market
+
+See references/public-api.md for the most useful routes, query params, and response cues.
+
+## Fast Paths
+
+### Find candidate endpoints
+
+1. Start with /v1/public/endpoints.
+2. Filter by q, protocol, paymentRail, sortBy, and freshOnly.
+3. Use certification, freshness, workflow health, incident pressure, and price signals together.
+4. Open the matching service or endpoint detail page before making a strong recommendation.
+
+### Compare providers or protocols
+
+1. Use /v1/public/endpoints for machine-readable search.
+2. Use /v1/compare or /v1/router when the user wants routing help or tradeoffs.
+3. Prefer fresh, certified endpoints over stale or docs-only listings.
+
+### Inspect live market or reliability movement
+
+1. Use /v1/signals for current movers, incidents, and notable changes.
+2. If the user wants a premium narrative summary, use /v1/signals/explain and expect an MPP payment challenge.
+3. Verify the underlying endpoint or service detail before escalating an alert.
+
+### Reuse an agent-facing interface
+
+If a service or namespace already exposes a generated skill, manifest, or client guide, prefer those surfaces before writing custom instructions:
+
+- /v1/services/:id/skill.md
+- /v1/services/:id/manifest.json
+- /v1/services/:id/client.md
+- /v1/namespaces/:namespace/skill.md
+- /v1/namespaces/:namespace/manifest.json
+- /v1/namespaces/:namespace/client.md
+
+## Task Guide
+
+### When the user wants discovery
+
+- Start with the public endpoint catalog, not a homepage scrape.
+- Search by capability or provider name, then filter by protocol and payment rail.
+- Use certification, health, freshness, and price data together. Do not rank on one field alone.
+
+### When the user wants the best endpoint
+
+- Clarify whether best means cheapest, freshest, healthiest, most autonomous, or most verified.
+- Prefer endpoints with recent proof, low incident pressure, and a matching authorization posture.
+- Call out when a listing is docs-backed or stale instead of runtime-fresh.
+
+### When the user wants onboarding or integration help
+
+- Look for service or namespace skill.md, manifest.json, or client.md surfaces first.
+- Use provider and service pages to gather docs, homepage, tags, related endpoints, and payment rails.
+
+### When the user wants trust or incident context
+
+- Read /v1/signals plus the service or endpoint detail.
+- Use certifications, open findings, workflow health, endpoint health, and incident history together.
+- Do not treat a listed service as endorsed just because it is indexed.
+
+## Usage Examples
+
+### Example prompts
+
+~~~
+Use mpp.directory to find fresh x402 or MPP endpoints for search, then rank the top options by verification quality and price.
+~~~
+
+~~~
+Look up this provider on mpp.directory, summarize its services and payment rails, and tell me which route looks safest for an autonomous agent.
+~~~
+
+~~~
+Check mpp.directory signals for anything relevant to MCP reliability this week, then explain the most important mover.
+~~~
+
+### Example reads
+
+~~~bash
+curl -fsSL 'https://mpp.directory/v1/public/endpoints?q=search&protocol=x402&freshOnly=true&limit=10'
+curl -fsSL 'https://mpp.directory/v1/services?limit=20'
+curl -fsSL 'https://mpp.directory/v1/providers'
+curl -fsSL 'https://mpp.directory/v1/signals'
+~~~
+
+## Reliability Rules
+
+- Treat /v1/public/endpoints as the primary machine-readable discovery surface.
+- Prefer fresh, certified, runtime-backed records over stale or docs-only records.
+- Do not assume a listed endpoint is cheap, public, or autonomous without checking pricing and authorization posture.
+- Use detail JSON or detail pages before making a strong claim about trust, incidents, or integration steps.
+- Treat paid /v1/signals/explain as optional analysis, not the source of truth.

mpp-directory/references/public-api.md

@@ -0,0 +1,115 @@
+# Public API Notes
+
+Use this file when you need quick route-level guidance without reloading the full skill into context.
+
+## Core Discovery
+
+### GET /v1/public/endpoints
+
+Primary machine-readable catalog for routing and comparison.
+
+Useful query params:
+
+- q: free-text search across provider, service, and endpoint metadata
+- protocol: mpp, l402, x402, a2a, or mcp
+- paymentRail: filter by payment rail such as tempo, x402, api_key, or free
+- sortBy: default, proof, telemetry, trust, governance, evidence, health, workflow, paid_reliability, value, price, or updated
+- freshOnly: restrict to recently refreshed endpoints
+- limit, offset: pagination
+
+The response carries far more than URL plus method. The highest-signal fields are usually:
+
+- endpoint: transport, HTTP method, payment rail, verification status, approval posture
+- service: display name, docs URL, homepage, tags
+- provider: provider family, source type, documented profile
+- certification: public trust summary and freshness windows
+- workflowHealth, endpointHealth, serviceHealth
+- recentPaid, openFindings, freshness, priceEngine
+
+## Directory Lists and Lookup
+
+### GET /v1/services
+
+Paginated service list for broad browsing or follow-up by service id.
+
+### GET /v1/providers
+
+Provider list for platform-level discovery and grouping.
+
+### POST /v1/services/lookup
+
+Use when you already know a likely service name, docs URL, homepage, or endpoint URL and want to match it to a registry record.
+
+Example payload:
+
+~~~json
+{
+  "displayName": "AgentMail",
+  "homepageUrl": "https://agentmail.to",
+  "docsUrl": "https://docs.agentmail.to",
+  "endpoints": [
+    {
+      "url": "https://mpp.api.agentmail.to/v0/inboxes",
+      "httpMethod": "GET"
+    }
+  ]
+}
+~~~
+
+## Detail Surfaces
+
+Use these once you have an id or namespace:
+
+- GET /v1/services/:id
+- GET /v1/services/:id/view
+- GET /v1/endpoints/:id
+- GET /v1/endpoints/:id/view
+- GET /v1/providers/:id
+- GET /v1/providers/:id/view
+- GET /v1/providers/by-slug/:slug
+- GET /v1/namespaces/:namespace
+- GET /v1/namespaces/:namespace/view
+
+Prefer the JSON routes when summarizing for another tool. Use the view routes when a human-readable detail page is more useful.
+
+## Agent-Facing Interfaces
+
+Some services and namespaces expose generated interfaces you can pass through to another agent or client:
+
+- GET /v1/services/:id/skill.md
+- GET /v1/services/:id/manifest.json
+- GET /v1/services/:id/client.md
+- GET /v1/namespaces/:namespace/skill.md
+- GET /v1/namespaces/:namespace/manifest.json
+- GET /v1/namespaces/:namespace/client.md
+
+These are often better starting points than inventing an integration guide from scratch.
+
+## Signals and Paid Explain
+
+### GET /v1/signals
+
+Live board for incidents, movers, spotlight entries, and market-style summaries.
+
+Use it when the user asks:
+
+- what changed recently
+- which services are rising or slipping
+- where reliability degraded
+- what looks newly valuable or risky
+
+### GET /v1/signals/explain
+
+Paid narrative expansion of a signal. Expect an MPP payment challenge on first access.
+
+Treat signals/explain as an interpretation layer. The underlying signal record plus the related service or endpoint detail remain canonical.
+
+## UI Routes
+
+These are useful when a user wants a human-facing entry point:
+
+- GET /v1
+- GET /v1/router
+- GET /v1/compare
+- GET /v1/market
+- GET /v1/signals/view