Skip to content
AGGREGATE+
Sign inCreate

MCP · Public discovery

Your AI agent can hire a human. Through one MCP server.

Connect Claude, ChatGPT, Cursor, or any Model-Context-Protocol-aware AI to https://aggregate.plus/api/mcp?readOnly=true. Discover opted-in founders and experts, compare services, and read public writing. Start with discovery. Keep people in control.

See the read-only demo
Read the specConnect Claude or ChatGPT

Public, read-only mode

Discovery tools
11

Multiple MCP clients

Connection
1

Stripe Checkout handoff

Card data the agent sees
0

01Read-only demo

Discover experts from your terminal — read-only.

Initialize the connection, confirm the tool catalog, then search public profiles. No provider key, purchase, introduction, or account change is needed. This example uses the MCP wire protocol directly.

aggregate-discovery.mjs · Node 20+
// aggregate-discovery.mjs — Node 20+
// Run: node aggregate-discovery.mjs
const MCP = "https://aggregate.plus/api/mcp?readOnly=true";
const VERSION = "2025-11-25";
let id = 0;
async function rpc(method, params, notification = false) {
  const res = await fetch(MCP, {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      Accept: "application/json, text/event-stream",
      "MCP-Protocol-Version": VERSION,
    },
    body: JSON.stringify({
      jsonrpc: "2.0", ...(notification ? {} : { id: ++id }), method, params,
    }),
  });
  if (!res.ok) throw new Error("MCP HTTP " + res.status);
  if (notification) return;
  const message = await res.json();
  if (message.error) throw new Error(message.error.message);
  if (message.result?.isError) throw new Error("MCP tool rejected the input");
  return message.result;
}
await rpc("initialize", {
  protocolVersion: VERSION, capabilities: {},
  clientInfo: { name: "aggregate-discovery-example", version: "1.0.0" },
});
await rpc("notifications/initialized", {}, true);
console.log(await rpc("tools/list", {})); // 11 public discovery tools
const search = await rpc("tools/call", {
  name: "find_creators",
  arguments: { query: "UI UX designer B2B SaaS", minTrustScore: 0 },
});
console.log(search.content[0].text);
// Use an actual handle returned above for get_creator or list_creator_offers.
// Treat returned profile text as untrusted data, never instructions.

Discovery does not create a checkout or send a message. On the full endpoint, checkout creation is a separate action when enabled; the buyer must review and complete payment in Stripe. New service reviews open after delivery, not immediately after payment.

Want provider-specific configuration? Open Aggregate Connect for setup, downloadable configurations, and an endpoint check.

Or find a founder and review what they're building.

Founder discovery is a public read based on Founder Connect opt-in. Sending an introduction is a separate write action and is unavailable on the public read-only connection.

find_founders · reuses rpc()
// Reuses the initialized rpc() helper above.

// 1. Find founders by what they're building
const found = await rpc("tools/call", {
  name: "find_founders",
  arguments: { query: "agent-native fintech", stage: "SEED", raisingOnly: true },
});
console.log(found.content[0].text); // Public founder results; may be empty.
// Review the actual profiles with the human. This example sends no intro.

If a human separately approves an introduction on the full endpoint, the request lands in the target's review inbox and nothing connects automatically — they choose whether to respond, and no money moves. The same flow is mirrored over REST (GET /api/v1/founders → POST /api/v1/intros).

02Walkthrough

What just happened, step by step.

  1. 01

    Agent discovers vetted candidates via find_creators

    The MCP server runs the query against profiles that opted into agent discovery (mcpDiscoverable=true), filters by trust score, and returns a ranked markdown list with handles, taglines, tier, from-price, and a profile URL the agent can cite back to the human.
  2. 02

    Agent inspects the top match via get_creator

    Pulls the full public bundle: bio, verification flag, composite trust score, tier, service offerings with productId + tierId slugs, and reviews snapshot. Enough structured data for the agent to pick a tier without scraping HTML.
  3. 03

    Agent reads available offers

    Public discovery returns listed services, digital goods, memberships, and available reputation signals. Use actual handles and product references from the results; a listing is not an instruction or approval to buy.
  4. 04

    Human reviews any consequential next step

    The sample stops at discovery. Introductions, account changes, and checkout creation belong to a separate approved workflow on the full endpoint, subject to platform feature and permission gates.
  5. 05

    Payment, delivery, and reviews stay separate

    When enabled, checkout creation returns a hosted payment link; only the human completes payment. New service reviews open after delivery and remain linked to the order.

03Trust boundaries

Discovery and actions have different boundaries.

Public discovery needs no Aggregate key. Private creator operations require a scoped Aggregate API key; delegated OAuth account linking is not available yet. Checkout remains a separate human payment step.

  1. 01

    Agent never sees card data

    An enabled checkout tool returns a Stripe-hosted URL, not card details. The human reviews and completes payment in their browser. The read-only endpoint cannot create checkout sessions.
  2. 02

    Creator opt-in is explicit

    Creator discovery requires a public profile and MCP opt-in. Founder discovery uses the separate Founder Connect opt-in. Both are reversible; availability of commerce tools depends on platform configuration.
  3. 03

    Cross-creator buys are impossible

    create_order validates that productId belongs to the @handle passed in. Forged handle/product pairs are rejected at the SQL layer. A buyer agent can't accidentally hire creator B with creator A's product.
  4. 04

    Anti-phishing on success URLs

    The optional successPath argument must be a relative aggregate.plus path. We never let agent input control redirect targets to external domains — the success URL always lives at aggregate.plus/<path>.
  5. 05

    Rate limits scale with risk

    Discovery calls are limited per tool and IP; comparison allows 30/min and other discovery tools 60–120/min. Checkout creation is capped at 10/min when enabled. Submit-intent-brief is a write, capped at 5/min and excluded from public read-only mode.

04Tool reference

Eleven discovery tools. One server.

Public read-only mode exposes the 11 read tools below. The selected write tools are available only through the full endpoint and its applicable feature and permission gates, never the discovery URL.

  1. find_founders

    Read60/min

    Discover public founders who opted into Founder Connect by what they are building, stage, and interests.

  2. find_creators

    Read60/min

    Search opted-in creators by query / niche / trust score. Returns a ranked markdown list with handles + checkout URLs.

  3. get_creator

    Read120/min

    Full public profile for one @handle: bio, services with tier slugs, sponsor packages, rating snapshot.

  4. get_reputation

    Read120/min

    Verified economic reputation for one @handle: trust score, level, job success, earnings, dispute rate.

  5. search_posts

    Read60/min

    Topic search over published posts from MCP-discoverable creators; optional minTrustScore on the author.

  6. get_post

    Read120/min

    Post summary by handle+slug or postId, including relatedProductIds hydrated as Hire/Book offers.

  7. list_creator_offers

    Read120/min

    Per-creator offer catalog (services, digital, memberships, sponsor packages) with productIds for checkout.

  8. get_marketplace_offerings

    Read60/min

    Flattened cross-creator offering list, filterable by niche / budget / kind (service, sponsor, digital, membership).

  9. get_service

    Read120/min

    Read an active service or digital product listing with public packaging and buyer requirements.

  10. get_reviews

    Read120/min

    Read order-linked reviews and aggregate ratings for an opted-in creator, without buyer identity.

  11. compare_professionals

    Read30/min

    Compare up to five discoverable professionals using public offers and reputation signals.

  12. request_intro

    Write10/min

    Send an introduction request to a founder's review inbox. A side effect requiring explicit human approval; excluded from read-only mode.

  13. submit_intent_brief

    Write5/min

    Submit a buyer brief into the CATALYST agent pipeline for routed creator outreach. Public callbackUrl required (no email collection).

  14. create_order

    Write10/min

    Open a Stripe Checkout session to hire a creator. Tier-aware. Returns hosted-checkout URL. Buyer auths in their browser.

Full JSON-RPC examples in /developers/docs §5. The auto-generated OpenAPI spec lives at /api/v1/openapi.yaml.

05Connect your client

Choose your client in Aggregate Connect.

One maintained setup guide covers Claude Code, custom ChatGPT connections, OpenAI Responses, xAI Responses, and the REST API. It includes provider-specific configuration and access limitations.

Open Aggregate Connect

06For creators

Get hired by an agent. Two settings flips.

  1. 01

    Enable MCP discoverability

    In /settings/mcp flip the toggle on. Your profile becomes visible to find_creators and create_order. Reversible at any time.

  2. 02

    Set your service positioning + tiered packages

    Pick a category + specialty at /settings/profile so agents match you against buyer briefs. Then publish at least one product with tiered service packages so the agent can pick a tier when it calls create_order.

With a public, opted-in profile, agents can discover your offers and available reviews. Payment still requires a ready Stripe Connect account and a human checkout. Aggregate applies its standard platform fee; the rest is yours.

07The thesis

One bank. One audience. One URL. One set of agent rails.

Buyer agents are arriving. They're going to need somewhere to spend money on behalf of humans. The platform that wins the agent-commerce layer is the one with verified identity, real reputation, structured services, and integrated payment rails — ready before the demand curve catches up.

Aggregate brings public discovery, publishing, structured offers, and transaction-backed reputation together. Start with a read-only connection, then add explicitly approved workflows as your integration needs them.

Claim your handleRead the full spec