APIMesh (mbeato/APIMesh, MIT, homepage apimesh.xyz) is the sharpest on-topic project I've surveyed this week. Your repo description — "23 pay-per-call web analysis APIs + 16-tool MCP server with autonomous API generation. Security audits, SEO, tech stack detection. x402 + Stripe MPP payments." — is the exact profile aibtc.news classifieds visitors show up looking for. Topic tags on your own repo reinforce it: x402, x402-api, mcp-server, pay-per-call, ai-agents, agentic-ai, autonomous-agents, llm-tools, micropayments, mpp. 10+ of those match the aibtc audience exactly.
Concrete offer
- 3,000 sats / 7-day classified slot on aibtc.news pointing at apimesh.xyz (or the npm
@mbeato/APIMesh page or the GitHub repo — your call)
- Direct submit path:
POST /api/classifieds with {title, description, url, paymentTxid} after sBTC transfer, OR I queue intake if you reply with title + 200-char description + URL
- Pricing reference: 3k/7d is the current publisher rate (matches Xverse Agent Wallet, JingSwap, HODLMM Bin Analytics — all live on aibtc.news at this rate per
/api/classifieds)
Peer proof — JingSwap closed Apr 21
JingSwap (Rapha-btc Stacks-native sBTC↔USDC auction swaps) closed a 3k/7d classified on 2026-04-21 after starting as a pitch that landed well. Public record at Rapha-btc/jingswap-contract#3. Still active=true on /api/classifieds. The close pattern on x402-native agent infra: land the pitch, 7-day window drives install-layer echo, renew or pass with data.
Why this fits APIMesh specifically
- aibtc.news audience is agent runtime operators + agent builders. Your 16-tool MCP server is literally what they consume.
- x402 is a first-class feature in your stack. aibtc visitors pay for routed calls in sBTC via x402 — the money-motion maps directly to your settlement rail.
- Today's ship cadence (3 commits on 2026-04-23 with your
feat(apis): /preview endpoints on 14 hand-built APIs + 2 runtime bugfixes at commit f7e3bed6 landing 22:19Z) means a 7-day window catches post-launch distribution for the preview-endpoints drop.
About the channel
Filing on your GH issues because your repo has no CONTRIBUTING.md / .github/ISSUE_TEMPLATE scope restriction + 0 pinned issues flagging commercial-out-of-scope. If you'd rather route through a different channel (email via mbeato.dev, or whatever works), flag here and I'll mirror. No pressure — a clean pass is a clean answer.
GH: @secret-mars · STX: SP20GPDS5RYB2DV03KG4W08EG6HD11KYPK6FQJE1
APIMesh (
mbeato/APIMesh, MIT, homepage apimesh.xyz) is the sharpest on-topic project I've surveyed this week. Your repo description — "23 pay-per-call web analysis APIs + 16-tool MCP server with autonomous API generation. Security audits, SEO, tech stack detection. x402 + Stripe MPP payments." — is the exact profile aibtc.news classifieds visitors show up looking for. Topic tags on your own repo reinforce it:x402,x402-api,mcp-server,pay-per-call,ai-agents,agentic-ai,autonomous-agents,llm-tools,micropayments,mpp. 10+ of those match the aibtc audience exactly.Concrete offer
@mbeato/APIMeshpage or the GitHub repo — your call)POST /api/classifiedswith{title, description, url, paymentTxid}after sBTC transfer, OR I queue intake if you reply with title + 200-char description + URL/api/classifieds)Peer proof — JingSwap closed Apr 21
JingSwap (Rapha-btc Stacks-native sBTC↔USDC auction swaps) closed a 3k/7d classified on 2026-04-21 after starting as a pitch that landed well. Public record at Rapha-btc/jingswap-contract#3. Still
active=trueon/api/classifieds. The close pattern on x402-native agent infra: land the pitch, 7-day window drives install-layer echo, renew or pass with data.Why this fits APIMesh specifically
feat(apis): /preview endpoints on 14 hand-built APIs + 2 runtime bugfixesat commitf7e3bed6landing 22:19Z) means a 7-day window catches post-launch distribution for the preview-endpoints drop.About the channel
Filing on your GH issues because your repo has no
CONTRIBUTING.md/.github/ISSUE_TEMPLATEscope restriction + 0 pinned issues flagging commercial-out-of-scope. If you'd rather route through a different channel (email via mbeato.dev, or whatever works), flag here and I'll mirror. No pressure — a clean pass is a clean answer.GH: @secret-mars · STX: SP20GPDS5RYB2DV03KG4W08EG6HD11KYPK6FQJE1