Vybe Pay MCP

Pay Collect offering

pay_offering

Start a Vybe Collect payment under the owner's connected spend key (OAuth Sign in or Bearer VAPT). Creates a pending pay and returns awaiting_approval — money does not move until the wallet owner taps Approve in Vybe (web or mobile). After paid (or trial), call use_paid_offering with the returned publicId — that unlocks research files, lists/runs seller MCP tools, or proxies paid API calls. Do not scrape the marketplace page. Pass username plus offeringId, or a Collect / marketplace offeringUrl. Related: use_paid_offering, fetch_paid_content, get_limits, get_spend_balance, list_recent_pays.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pay_offering"
  }
}

Input Schema

Name	Required	Description
`calls`	No	Optional. Buy a prepaid bundle of this many calls (see bundles in get_tool), usually cheaper per call. Omit it to use free calls and bundle calls first; when those run out, a tool that sells bundles charges for its smallest bundle, and only tools without bundles charge for one call.
`username`	No	Seller Collect username without the @ prefix, for example yellobots. Required with offeringId when offeringUrl is omitted.
`offeringId`	No	Collect offering id from the seller catalog, for example svc_gMcO7ioZ. Required with username when offeringUrl is omitted.
`offeringUrl`	No	Full Collect or marketplace URL for the offering, including tool pages like https://www.vybe.finance/marketplace/tools/{slug} (offeringUrl from search_tools). Use this instead of username plus offeringId when you already have the link.

Output Schema

Name	Required	Description
`ok`	Yes	true when the pay was created or a trial was granted.
`token`	No	Settlement token, typically usdc.
`amount`	No	USD amount as a decimal string, e.g. 0.02.
`status`	No	awaiting_approval means the owner must Approve in Vybe. trusted_awaiting means a connected merchant pay is queued quietly. trial means a free call was granted and prepaid means one call was spent from a bought bundle; neither needs Approve.
`unlock`	No	Exact unlock step: call use_paid_offering with publicId. Do not scrape marketplace HTML or invent seller HTTP calls.
`message`	No	Short instruction for the agent to show the user.
`publicId`	No	Vybe payment request id.
`invokeUrl`	No	After paid or trial: GET this URL with header X-Vybe-Public-Id set to publicId to receive the unlocked content.
`statusUrl`	No	Poll this URL for paid / pending / cancelled.
`approveUrl`	No	Link for the owner to Approve or Decline in Vybe.
`nextAction`	No	Machine-readable next step after Approve: which tool to call and with which publicId.
`offeringId`	No	Collect offering id, e.g. svc_…
`offeringType`	No	Collect offering type: mcp, api, asset, session, etc.
`offeringTitle`	No	Human title of the offering.
`sellerUsername`	No	Collect seller username without @.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this as a non-read-only, non-idempotent, open-world write, so the safety bar is partly covered. The description adds the crucial behavior that the call only creates a pending pay and money does not move until the owner approves in Vybe, plus the awaiting_approval return state and the auth modes (OAuth Sign in or Bearer VAPT). It doesn't address retry/duplicate-pay behavior even though idempotentHint is false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The primary action and the approval caveat are front-loaded, and each sentence carries a rule, a next step, or an anti-pattern. The trailing "Related:" list is somewhat listy but functional and short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be explained, yet the description still names awaiting_approval and publicId as the handoff token. For an open-world payment mutation with four optional params, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3; the schema already explains calls, username, offeringId and offeringUrl in more detail than the description does. The description restates the username+offeringId versus offeringUrl rule but adds no meaning beyond it and says nothing about the calls bundle parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Start a Vybe Collect payment under the owner's connected spend key") plus the scope constraint of whose key is used. It also implicitly separates itself from sibling flows like use_paid_offering by naming that tool as the next step rather than an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit input routing ("Pass username plus offeringId, or a Collect / marketplace offeringUrl") and an explicit exclusion ("Do not scrape the marketplace page"). It also states the follow-up condition: after paid or trial, call use_paid_offering with the returned publicId.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vybe Pay MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?