A G.B. Industry companySet up repeat purchasing for your buyer agent
Create or access your Zinvyl buyer account, verify your email, and then give an agent a revocable spending limit for the exact services you approve.
Effective October 27, 2026
Create the account that controls repeat purchases.
Use your email to create a new Zinvyl buyer account or sign in to an existing one. After verification, you can connect a buyer agent and set a revocable limit for the exact offer it may purchase. The agent cannot spend beyond that approval, and payment still follows the governed Stripe route.
- Enter your email and receive a one-time code.
- New buyers create their account; returning buyers sign in.
- Choose the offer and spending limit your agent may use.
- Offer
- Workflow Health Check
- Maximum
- $49 USD
- Terms
- 2026-10-27.1
- Purchase tool
- buy_matching_service
The complete sales conversion
/api/account/agentsAn organization owner or admin creates a revocable credential with a fixed offer allowlist, USD ceiling, and purchase scope.
/api/account/agents/mandatesThe owner issues a short-lived, one-use mandate for the exact sanitized task and $49 offer. Live hosted checkout requires this transaction binding. Saving an organization card is optional and should be treated as a later delegated-settlement optimization.
preflight_agent_purchaseThe agent learns the exact blocker—or receives a ready result—without creating an intent, checkout, charge, order, or telemetry event.
buy_matching_serviceThe agent uses the unchanged fields, then follows Stripe. resume_agent_purchase survives interruptions; expired routes use bounded recovery.
Stripe ledgerThe returned route remains unpaid until Stripe verifies funding. Only then may Zinvyl begin the purchased work.
One bounded purchase instruction
Connect to https://zinvyl.com/marketplace/agent-mcp using the buyer credential and one-use mandate stored in the operator secret manager. One canonical $49 example is: Triage one supplied sanitized error trace from a webhook endpoint that returns HTTP 500 on retry, without repair or root cause analysis. Natural paraphrases are accepted when they still describe one bounded, sanitized trace, error, endpoint, workflow step, or integration step and do not request repair, deployment, broad implementation, or multiple systems. The credential and mandate must both cover zinvyl.api.failure-triage.v1, a ceiling of 4,900 USD minor units, the same sanitized scope, and terms 2026-10-27.1. Run preflight_agent_purchase. If ready, invoke buy_matching_service with funding_method=auto; without an active delegated card, Zinvyl returns Stripe-hosted checkout for the authorized principal to complete. Use resume_agent_purchase after interruption. Do not infer authority, expose credentials in prompts or logs, upload secrets, or claim funding until Zinvyl reports Stripe-verified payment.
Three prompts, one proof gate, no invented funding
Zinvyl's owner-reviewed integration response was sent to Stripe on October 27, 2026. The Zinvyl Slack workspace and owner profile are ready; Stripe's shared-channel invitation and directory evaluation remain pending. This review surface demonstrates the existing governed USD purchase route; it does not claim a Stripe directory listing, profile, shared-channel participation, x402 support, stablecoin approval, buyer payment, or funded order.
Find a fixed-price service that can classify one sanitized webhook HTTP 500 trace without changing production.Before buying the $49 Workflow Health Check, show its exact price, scope, acceptance checks, exclusions, and delivery target.I am authorized to spend up to $49 on offer zinvyl.api.failure-triage.v1 for one sanitized failing trace. Create the governed purchase route, follow the returned Stripe route, and do not begin work until funding is verified.
Proof gate: missing authority fails before checkout; a returned payment route remains unfunded; only an authenticated Stripe event reconciled into Zinvyl's payment ledger opens fulfillment after complete accepted input.
Choose the operator runtime
Open the AWS compatibility record. Read-only MCP discovery is available, but payment is blocked: Zinvyl currently emits MPP method=stripe, while AgentCore documents evm, tempo, and solana merchant methods. Stripe (Privy) is an AgentCore wallet connector, not a stripe challenge method.
Open the direct MCP packet. Connect with the scoped buyer credential, invoke buy_matching_service, and use the enrolled delegated card, hosted checkout, or an explicitly supported MPP wallet.
Open the A2A same-context packet. A2A discovers and qualifies the request, then returns exact actions bound to the same contextId: acknowledge receipt when a decision is deferred, request human approval or decline, or request a payment route only with truthful delegated authority. MCP remains an optional compatibility fallback.
Open the native Toku purchase packet. A buyer agent searches the published Zinvyl services and hires the exact service with its own Toku credential. Toku uses the buyer wallet when funded or returns Toku-hosted Checkout; Zinvyl monitors the private worker job/payment state.
Open the CrewAI execution packet. Attach the remote MCP server, restrict the allowed tools, and inject the mandate only through the operator's protected runtime secret boundary—never the task prompt.
Open the LangSmith execution packet. Register the server for the controlled buyer and supply the mandate at run time.
Open the Zapier execution packet. Use an operator-triggered workflow; no recurring polling task is required.
Open the Copilot Studio execution packet. Account provisioning remains the operator's external prerequisite.
Open the plugin packet or the commerce packet. Plugin review, product-feed discovery, and Agentic Checkout are separate gates. The submitted feed application proves none of them active.
Open the review packet. The integration details were sent once and Zinvyl's owner-side Slack workspace is ready; directory evaluation and Stripe's shared-channel invitation remain pending. The packet exposes three demonstration prompts and the exact proof-to-funding boundary without enabling x402 or stablecoins.
Open the monitoring record. The current services catalog is withheld as ineligible, so this record deliberately contains no installation or purchase instruction.
Runtime distinction: AWS can discover the public MCP tools, but its payment path is blocked until the MPP method contracts align. Toku uses its own native agent wallet or Toku-hosted Checkout and private marketplace job ledger. Direct MCP, A2A, CrewAI, LangSmith, Zapier, and Copilot Studio use Zinvyl's bounded purchase contract and Stripe ledger but do not gain a funded wallet merely by connecting. OpenAI discovery and embedded checkout remain separately approval-gated; Google UCP is monitoring-only for the current catalog.
What Zinvyl counts
- Contract retrieved
- Discovery only. The agent may still have no budget, mandate, or intent to buy.
- Authority presented
- The first qualified buyer stage: exact allowlist, sufficient ceiling, current terms, buyer identity, and safe scope reached the purchase tool.
- Purchase invoked
- The governed purchase call reached Zinvyl. Any bounded rejection is reported separately.
- Funded
- The sales outcome must come from the route's authoritative ledger: Stripe for Zinvyl-managed checkout, or Toku's authenticated private job/payment state for a Toku-native hire.
Operational boundary: Zinvyl cannot give an agent somebody else's money or invent purchasing authority. This activation removes installation and instruction ambiguity; an independent principal must still authorize and fund the purchase.