AGENT SETUP + REVIEW

Connect an agent to Zinvyl

Zinvyl exposes a public, authentication-free, read-only MCP endpoint for offer discovery, task qualification, acceptance-test inspection, and preparation of an external payment route. It cannot charge a buyer or declare an order funded.

Effective September 20, 2026

STREAMABLE HTTP ENDPOINThttps://zinvyl.com/marketplace/agent-mcp

Server name: com.zinvyl/marketplace · Transport: Streamable HTTP · Authentication: none for public routing tools

A2A discovery

A2A-compatible agents can discover Zinvyl through the public Agent Card and send a sanitized qualification request to POST /marketplace/a2a/message:send. The A2A route returns a completed, structured qualification task only; use MCP for acceptance-test inspection and authorized payment-route preparation.

Connect

  1. Open the MCP or custom-connector settings in a compatible agent client.
  2. Add a remote Streamable HTTP server using the endpoint above.
  3. Confirm the client discovers exactly four tools: list_offers, qualify_task, get_acceptance_tests, and prepare_purchase_route.
  4. Keep tool approval enabled while evaluating the connector. Never place secrets, credentials, regulated data, or raw confidential files in a public routing call.

Recommended tool sequence

01Discoverlist_offers

Compare the fixed prices, delivery windows, required inputs, exclusions, and intake routes.

02Qualifyqualify_task

Map one sanitized expected-versus-actual outcome to an offer or a safe non-offer route.

03Verify scopeget_acceptance_tests

Retrieve the exact delivery tests, exclusions, and limits for the selected offer.

04Prepare fundingprepare_purchase_route

Only with explicit purchasing authority, retrieve the schema and external payment-route endpoint.

Post broader work as an authorized buyer

If neither fixed offer fits, an authorized human or purchasing agent can submit one sanitized, bounded outcome to POST /marketplace/api/network/request. Validate the body against the work-request schema and follow the work-request contract. Agent requests require an HTTPS identity endpoint, a unique Idempotency-Key, and a delegated limit that covers the maximum budget. A successful response creates only an unfunded review receipt; it does not create a match, contract, payment, or permission to begin work.

Working prompt examples

DISCOVERY

Using Zinvyl, list the available fixed-scope offers. Compare price, delivery window, required inputs, and exclusions. Do not request a payment route.

FREIGHT QUALIFICATION

Using Zinvyl, qualify this sanitized task: “Carrier invoices, bills of lading, and proofs of delivery are manually compared before a load is approved.” Return the recommended offer ID and reason. Do not diagnose the workflow.

CONTROLLED PURCHASE HANDOFF

Using Zinvyl, retrieve the acceptance tests for zinvyl.freight.workflow-audit.v1. If—and only if—I explicitly authorize the published $199 fixed fee, prepare the external payment route. Do not claim the order is funded or started.

Expected safety behavior

The connector returns routing information only. prepare_purchase_route requires a true purchasing-authority assertion, but even a successful response remains unfunded. The external payment route creates a purchase intent and redirects to Stripe-hosted checkout. Only a matching signed Stripe webhook recorded in the G.B. Industry payment ledger can verify funding. Scope confirmation and complete intake remain separate gates before work starts.

Reviewer test

No test account or customer data is required. Call list_offers, qualify either example above, retrieve the selected offer's acceptance tests, and call prepare_purchase_route once with purchasing authority set to false. The final call should return authorization_required and funding_state: unverified.

Troubleshooting

The server is not discovered
Confirm the complete HTTPS endpoint is used, the client supports remote Streamable HTTP MCP servers, and outbound HTTPS is permitted.
A tool rejects the request
Use the exact published offer ID. Keep task summaries between 20 and 3,000 characters and remove credentials, tokens, personal data, production secrets, and raw confidential files.
No payment route is returned
The agent must have explicit authority for the published offer and fee. A buyer who lacks that authority must obtain approval from an authorized representative.
Checkout succeeded but status is pending
Do not pay again. Webhook reconciliation can take a short period. Use the returned order-status route; only the signed ledger record determines funding.

Support and policies

Contact Zinvyl. Review the Privacy Policy, Security Statement, Acceptable Use Policy, and Terms before connecting the service to production workflows.