Zinvyl Marketplace Agent Gateway

Create an authorized purchase intent

create_purchase_intent

Use after selecting one offer when the calling agent has explicit delegated authority for that exact fixed fee. Creates the governed purchase intent and quote, then returns the no-human Stripe MPP route plus a human Checkout fallback. It does not itself claim payment or start work.

Input Schema

TableJSON Schema

Name	Required	Description
`offer_id`	Yes	Exact published offer ID returned by list_offers or qualify_task.
`task_summary`	Yes	Sanitized, bounded task summary. Never include credentials, tokens, payment data, personal data, confidential files, or production secrets.
`terms_accepted`	Yes	True only when the authorized buyer has accepted Zinvyl terms version 2026-10-05.1.
`buyer_organization`	Yes	Legal or operating name of the buying organization.
`buyer_contact_email`	Yes	Email for the authorized purchasing contact and order communications.
`bounded_scope_confirmed`	Yes	True only when the buyer controls the inputs and this sanitized request is non-production and contains no secrets.
`delegated_purchase_authority_confirmed`	Yes	True only when the agent is acting within explicit delegated authority for this exact offer and published amount.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / offer_id / enum

Previous value: -[
-  "zinvyl.venture.evidence-brief.v1",
-  "zinvyl.venture.prototype-scope.v1",
-  "zinvyl.freight.workflow-audit.v1",
-  "zinvyl.api.workflow-failure-rescue.v1",
-  "zinvyl.api.failure-triage.v1",
-  "zinvyl.freight.full-workflow-audit.v1"
-]New value: +[
+  "zinvyl.venture.evidence-brief.v1",
+  "zinvyl.venture.prototype-scope.v1",
+  "zinvyl.freight.workflow-audit.v1",
+  "zinvyl.api.workflow-failure-rescue.v1",
+  "zinvyl.api.failure-triage.v1",
+  "zinvyl.freight.full-workflow-audit.v1",
+  "zinvyl.content.ai-marketing-pilot.v1"
+]

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / terms_accepted / description

Previous value: -"True only when the authorized buyer has accepted Zinvyl terms version 2026-09-26.1."New value: +"True only when the authorized buyer has accepted Zinvyl terms version 2026-10-05.1."

Changed8 schema fields changedOct 5, 2026

addedInput schema / properties / bounded_scope_confirmed

Added value: +{
+  "description": "True only when the buyer controls the inputs and this sanitized request is non-production and contains no secrets.",
+  "type": "boolean"
+}

removedInput schema / properties / buyer_contact_name

Removed value: -{
-  "description": "Authorized human principal or purchasing contact.",
-  "maxLength": 200,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / buyer_note

Removed value: -{
-  "description": "Optional sanitized purchasing note.",
-  "maxLength": 2000,
-  "type": "string"
-}

removedInput schema / properties / funding_method

Removed value: -{
-  "description": "Requested Stripe-hosted payment method. Availability is determined by Stripe at checkout.",
-  "enum": [
-    "stripe_hosted_card",
-    "stripe_hosted_ach"
-  ],
-  "type": "string"
-}

removedInput schema / properties / no_secrets_in_payload

Removed value: -{
-  "description": "True only after confirming this request contains no credentials, payment data, private keys, or other secrets.",
-  "type": "boolean"
-}

removedInput schema / properties / non_production_only

Removed value: -{
-  "description": "True only when public routing and the initial scope use sanitized, non-production inputs.",
-  "type": "boolean"
-}

removedInput schema / properties / owns_or_controls_inputs

Removed value: -{
-  "description": "True only when the buyer owns or is authorized to provide every described input.",
-  "type": "boolean"
-}

changedInput schema / required

Previous value: -[
-  "offer_id",
-  "buyer_organization",
-  "buyer_contact_name",
-  "buyer_contact_email",
-  "task_summary",
-  "delegated_purchase_authority_confirmed",
-  "owns_or_controls_inputs",
-  "non_production_only",
-  "no_secrets_in_payload",
-  "funding_method",
-  "terms_accepted"
-]New value: +[
+  "offer_id",
+  "buyer_organization",
+  "buyer_contact_email",
+  "task_summary",
+  "delegated_purchase_authority_confirmed",
+  "bounded_scope_confirmed",
+  "terms_accepted"
+]

AddedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare it is a non-read-only, non-idempotent, open-world write. The description adds meaningful context beyond that: it produces a quote plus two payment routes (no-human Stripe MPP and human Checkout fallback) and explicitly does not charge or start work. It does not warn about duplicate creation, which matters given idempotentHint=false.

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

Conciseness5/5

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

Three tight sentences with the precondition front-loaded, followed by what the call produces and what it explicitly does not do. No filler and no repetition of schema content.

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

Completeness4/5

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

For a mutation tool with no output schema, the description conveys the key return artifacts (governed intent, quote, MPP route plus Checkout fallback) and the safety boundary that payment is not claimed. Missing only idempotency/duplicate-handling guidance, which the idempotentHint=false annotation leaves the agent to infer.

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 all seven parameters, including the confirmation flags and the offer_id enum, are already documented in the schema. The description adds no parameter-level detail such as format or constraint beyond the 'exact fixed fee' framing, so the baseline 3 applies.

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?

Names a specific verb and resource ('Creates the governed purchase intent and quote') and states the exact trigger condition ('after selecting one offer'). It also bounds what the tool is not ('does not itself claim payment or start work'), which distinguishes it from sibling pre-purchase tools like qualify_task and prepare_purchase_route.

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

Usage Guidelines4/5

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

Gives a clear precondition sequence: use only after one offer is selected and only when the agent has explicit delegated authority for that exact fixed fee. It does not name alternative siblings or state what to do when authority is absent, so it stops short of full routing guidance.

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

All Zinvyl Marketplace Agent Gateway 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?