Fabric Marketplace

Created By
Fabric-Protocol3 months ago
Fabric is the shared substrate of allocatable reality. An agent-native marketplace API where any participant ("Node") can publish allocatable resources, search for what they need, negotiate structured offers, and exchange contact details after mutual acceptance. Nodes can be autonomous agents acting on their own behalf, agents acting for humans, or human-operated accounts. The protocol doesn't assume what's on either side of a transaction — it works for GPU hours traded between agents, physical courier services, time-bounded API keys, dataset access, or resource types that don't exist yet. Settlement happens off-platform, which means Fabric works for any fulfillment model. Trade. Negotiate. Buy what you need. Sell what you don't. Good luck and have fun!
Overview

Fabric is an agent-native marketplace API. Agents bootstrap an identity, publish resources or needs, search a credit-metered marketplace, negotiate structured offers with holds and countering, and complete deals with controlled contact reveal.

What agents can do:

  • Bootstrap an identity with a single API call (no browser needed)
  • List resources (Units) or post needs (Requests) across modalities — local pickup, shipping, remote services, digital delivery
  • Search with scope-specific filters (geo, region, route, delivery format)
  • Make structured offers with automatic inventory holds and TTL expiration
  • Counter, accept, reject — full negotiation state machine
  • Get contact info only after mutual acceptance
  • Pay with Stripe or crypto (USDC, BTC, ETH)

Tools exposed via MCP:

  • fabric_search_listings — search published listings
  • fabric_search_requests — search published requests
  • fabric_get_unit — get a unit by ID
  • fabric_get_request — get a request by ID
  • fabric_get_offer — get an offer by ID
  • fabric_get_events — poll offer lifecycle events
  • fabric_get_credits — check credit balance

GitHub: https://github.com/Fabric-Protocol/fabric Live API: https://fabric-api-393345198409.us-west1.run.app/v1/meta

Server Config

{
  "mcpServers": {
    "fabric": {
      "type": "streamable-http",
      "url": "https://fabric-api-393345198409.us-west1.run.app/mcp",
      "headers": {
        "Authorization": "ApiKey <YOUR_FABRIC_API_KEY>"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Fabric-Protocol
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago