feat: add Tack IPFS pinning service

[kimo-ice]

Summary

• Adds Tack (tack.inferenceroom.ai) to the MPP service registry
• Tack is an IPFS pinning and content retrieval service with native MPP support (USDC.e on Tempo via mppx)
• First-party integration — tack handles MPP payment verification and settlement directly

Service details

Field	Value
id	tack
categories	["storage"]
integration	first-party
realm	tack.inferenceroom.ai
payments	Tempo USDC.e
pricing	dynamic ($0.10/GB/month, min $0.001)

Endpoints covered

• POST /pins — Pin by CID (dynamic price)
• POST /upload — Upload + pin file (dynamic price)
• GET /ipfs/:cid — Retrieve content (free by default; optional owner-set paywall via meta.retrievalPrice)
• GET /pins, GET /pins/:requestid, POST /pins/:requestid, DELETE /pins/:requestid — Owner management (bearer token)

Discovery surfaces (all live)

• homepage: https://tack.inferenceroom.ai
• llmsTxt: https://tack.inferenceroom.ai/llms.txt
• apiReference: https://ipfs.github.io/pinning-services-api-spec/
• A2A agent card: GET /.well-known/agent.json ✅
• OpenAPI 3.1 (AgentCash discovery): GET /openapi.json ✅

Checks

• pnpm check:types — passes (after node scripts/generate-discovery.ts to regenerate schemas/discovery.json)
• pnpm check (biome) — passes (no fixes needed after --write)
• pnpm check:sdk-drift — pre-existing failure on main (unrelated to this PR; same set of mppx exports flagged before tack was added)
• categories: ["storage"] — confirmed valid enum value in CATEGORIES

Verification

$ curl -s -o /dev/null -w "%{http_code}\n" https://tack.inferenceroom.ai/
200
$ curl -s -o /dev/null -w "%{http_code}\n" https://tack.inferenceroom.ai/llms.txt
200
$ curl -s -o /dev/null -w "%{http_code}\n" https://tack.inferenceroom.ai/.well-known/agent.json
200
$ curl -s -o /dev/null -w "%{http_code}\n" https://tack.inferenceroom.ai/openapi.json
200

[vercel]

@kimo-ice 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!

If you want your service included in the curated mpp.dev/services list, complete this checklist before review:

Required

• Your service is live and accepting payments via MPP (not a placeholder or coming-soon)
• You've added your entry to schemas/services.ts following the contributing guide
• Types pass: pnpm check:types
• Build succeeds: pnpm build

Recommended

• Register your service on MPPScan (by Merit Systems) — it follows the standard MPP discovery format and makes your service discoverable by agents immediately, no PR required

Review criteria

We prioritize services that are high quality and novel. We may not approve services that duplicate existing functionality or aren't yet production-ready.

---

Contributing guide · MPPScan · Protocol docs

[github-actions]

🔀 Changed Services

✅ Added

• tack