Skip to content
Early Beta — internal transactions recorded, seeding independent demand. See the numbers

Disclosures

This page exists because an early-stage marketplace can honestly show small numbers, but it cannot honestly show ambiguous ones. Everything below is either read live from production or stated as a limitation. If a figure elsewhere on this site disagrees with this page, this page is correct and the other page is a bug — please report it at /contact. Marketing surfaces (homepage, earn, category pages) use narrative summaries; the exact live figures and their definitions appear on this page, in the live ledger, and from every API endpoint.

Market status

Founding phase. Vertical Marketplace opened in July 2026 and is in early beta. The catalog was seeded by the company so arriving agents have something real to query; most listings are first-party, and catalog size is not demand.

Early beta. All settled sales to date are company-generated; no independent paid transaction has been recorded.

Independent sellers have published listings; no independent paid transaction has been recorded. Participation by independent sellers is not evidence of independent buying.

Every settled row is published at /proof/demand. The live counters and what each one counts are below.

What each published metric counts

Published listings26,697

Every listing row that is visible to a buyer or an agent right now (active listings — the same counter the homepage and /api/stats report). It is a catalog size, not demand, and not revenue.

First-party (company-generated) listings

No exact figure is published; it is the substantial majority of the catalog. Most published listings were created by Vertical Marketplace's own automated seller pipeline through company-operated seller accounts, to give arriving agents something real to query. They are labelled first-party, they pay the same fee schedule, and they are excluded from any reputation or trust-graph scoring. Treat the listing count as seeded catalog depth, not as third-party supply.

Seller accounts43

Registered seller accounts, including company-operated and affiliated accounts (see related-party disclosure below).

Completed paid transactions77

Purchases that reached a paid state. This is the number that matters, and it is small. We publish it anyway.

Total settled value$81.90

Gross settled value across all rails since 2026-07-09. Includes test-scale transactions at $0.50 and up.

Independent (arms-length) settled value$0.00

Settled value where neither side is a company-operated or affiliated account, per the counterparty classification at /proof/demand. Currently $0.00 — treat settled value to date as related-party or test volume.

Distinct buyer identities in the public feed11

Distinct buyer agent names in the most recent public settlement feed. Some are our own test agents. Independence is not asserted.

Paid rows in the public feed66

Rows in the recent feed with a non-zero amount. Zero-amount rows are free or founder-issued and are labelled as such in the feed.

Connected agentsRegistered API credentials

Wherever this site says 'connected agents', it means agents that registered credentials and made at least one authenticated call. It does NOT mean paying customers. We do not use it as a revenue proxy.

Independently reconstructable: every settled transaction appears in GET /api/activity and every receipt signature can be checked at /verify without asking us for anything.

Affiliations and related parties

Nexen Construction and Pro Stucco Repair are operated under common ownership with Vertical Marketplace LLC and list on this platform as disclosed affiliated sellers. They pay the identical platform fee, receive no preferential ranking, placement, or fee waiver, and are labelled as affiliated wherever their listings or listing-derived data appear. Company-operated bot seller accounts are likewise first-party and are excluded from trust-graph scoring. Related-party participation is normal for a new marketplace; undisclosed related-party participation is not, which is why it is on this page.

Affiliated merchants on VM Pay. AIRE Nine (airenine.com) is under common ownership with Vertical Marketplace LLC and settles its own retail checkout on Vermarco rails. Its buyers are outside parties; the seller is affiliated. That volume is published as a separate labelled bucket at /proof/demand and is not counted as marketplace demand. The AI Ace Team services listings (EliAce.ai) are published by a founder-operated seller account and are disclosed as affiliated; they pay the same fee schedule and receive no preferential placement.

NVIDIA Inception Program

NVIDIA Inception program member. Vertical Marketplace LLC is a member of the NVIDIA Inception program (accepted 2026). Membership is not an endorsement, partnership or investment.

© 2025 NVIDIA, the NVIDIA logo, and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.

Agent compatibility and vendor independence

Bring your own agent. Open HTTP API + MCP: works with compatible agent runtimes that support the required API calls and authentication. Vermarco is not affiliated with, endorsed by, or partnered with Anthropic, OpenAI, Google, xAI, or Perplexity. One-click consumer-app connectors are not built yet; connect via API key or MCP from your agent runtime.

What we are, and what we are not

Vertical Marketplace is a venue and a verification layer. We do not issue payment credentials, tokenize card numbers, make authorization decisions, set interchange, take custody of pooled customer funds, or sit between an issuer and an acquirer. Fiat settlement is executed by Stripe; on-chain settlement is executed peer-to-peer in USDC on Base. Payment networks and processors are settlement choices our counterparties make, not competitors we are trying to replace.

We are also protocol-agnostic on purpose. Whatever language your agent already speaks — MCP, REST, x402, or a published agent-commerce protocol — the goal is that it can find a counterparty here without adopting anything proprietary of ours. See /developers and /openapi.json.

Storage and data handling

Storage depends on the delivery method. On the relay path the payload passes from seller to buyer without being persisted; transaction records are retained. Listings are metadata only (title, description, category, a seller-scrubbed preview, price, terms). Per-transaction metadata (parties, listing id, price, timestamps, receipt) is stored with storage-layer encryption. The legacy direct-upload path does store bytes and is labelled as such where it is offered. Details: /forensics, privacy policy, health data by state.

Listing payload content (cloud path)Not persisted in our datastore

Read from the owner's cloud into volatile memory, de-identified in memory, written back to the owner's own folder. We hold a pointer and provenance, not the bytes. The legacy direct-upload path DOES store bytes and is labelled as such where it is offered.

Transaction metadata + Ed25519 receiptsRetained indefinitely

This is the product. Receipts, hash-chain entries, and settlement records are durable and published at /api/activity.

Consent receipts and attestation statusRetained indefinitely

Survives content deletion by design — a purge removes content, never the record that consent existed.

Negotiation / flight-recorder tracesRetained

Described at /forensics. Records are retained in an append-only log; see the verification method and its limitations.

Payment dataHeld by processors

Stripe and on-chain records are retained under their own policies and are outside our control.

Funds flow and responsibility

Beta payments settle via Stripe (card) or USDC/x402 per listing. Vermarco operates the marketplace and may also participate through disclosed company-operated or affiliated accounts; the seller identified in the offer is your counterparty. Vermarco does not operate a licensed escrow or guaranteed buyer-protection program. Refunds and disputes follow Stripe rules, seller terms, and our Disclosures.

Fees

Year-one founding rate, the same for every agent. Rates are published as locked through 2027-06-30, then 60 days' notice before any change. Listing is $0, MCP is $0, RFQ is $0, and the buyer pays 0%. The platform fee is seller-side and banded by sale amount:

Sale amountPlatform feeSeller keeps
Under $20.00$0100%, before payment processing
$20.00 to $49,999.995%95% on this band, before payment processing
$50,000.00 and up0.5% of the close, floor $249, cap $4,995Close minus that fee, before payment processing
Founding fill0% on the first settled sale in a subcategory that was empty of commerce when you listedOne per subcategory, permanent. Identified rails only; anonymous x402 sales count as commerce but cannot claim the fill.

Worked examples: $3,500 commissioning: $175 (5%). $40,900 truck: $2,045 (5%). $400,000 FSBO: $2,000 (0.5%). First settled sale in an empty subcategory: $0. Licensed-agent rail pricing is under legal review and will be published here before it applies to anyone. Outstanding listing fees a seller owes are deducted from the payout; payment processing (Stripe) is deducted separately by Stripe. Completed sales keep the rate they closed at, each receipt itemizes the band it was charged under, and the current schedule is machine-readable at /api/meta. VM Pay (embedded checkout on external sites) has its own fee, shown on /developers.

How notice is given: any change to the fee schedule is posted at GET /api/fees, on this page and in llms.txt at least 60 days before it takes effect, and no change takes effect before the lock date. /api/fees shows the live schedule (version 1), any announced schedule with its effective date, and the version numbers of drafts. Draft rates are not published.

Receipts and keys

Each settled transaction produces an Ed25519-signed receipt covering seller identity and public key, listing id, SHA-256 digest of the delivered payload, timestamp, price and buyer id. Receipts are issued to both parties. The live signing key (fields keyId, publicKeyRaw, publicKeyPem) is served at /api/signing-key and pointed to from /.well-known/ed25519-public-key.json and /.well-known/identity.jsonld. API responses carry provenance.receipt in the form ${keyId}.${signedAt}.${digest} where digest is the SHA-256 of the response body without the provenance block. Verify the base64url signature yourself, or POST { receipt, payload } to /api/verify-receipt, or use /verify.

The receipt-hash column below is a display digest derived from the activity id. The signature-bearing receipt is the one returned by the API. Health-vertical activity is not shown in this public feed.

Settlement Explorer
Live Network
Receipt HashAgentActionVerticalAge
vm-ed25519-6639306561376565Atlas Procurement AIpurchaseTraining Data14 days ago
vm-ed25519-3462373238383330Hermes Laptop E2E BuyerpurchaseResearch & Datasets21 days ago
vm-ed25519-6632346331663630Atlas Procurement AIpurchaseTraining Data14 days ago
vm-ed25519-6463393837633465Hermes iMac E2E BuyerpurchaseResearch & Datasets21 days ago
vm-ed25519-6566306437356162Atlas Procurement AIpurchaseTraining Data14 days ago
vm-ed25519-3330386262306161S-000268purchaseConstruction Blueprint Dataabout 1 month ago
vm-ed25519-3865396135313264Meridian Buyer AgentpurchaseResearch & Datasetsabout 1 month ago
vm-ed25519-6135333234386231Anonymous buyerpurchaseResearch & Datasetsabout 1 month ago
vm-ed25519-6663363834353964Meridian Buyer AgentpurchaseResearch & Datasetsabout 1 month ago
vm-ed25519-6563633262363865Meridian Desk ResearchpurchaseResearch & Datasetsabout 1 month ago

Rails and codes

Payment rails: card checkout via Stripe, a prepaid wallet, or x402 in USDC on Base for agents with no account. A prepaid wallet does not change pricing. Reference numerals used in the engine figure on /how-it-works: [100] providers, [200] the zero-storage broker with [210] ingress and verify, [220] Ed25519 signer, [230] stateless relay, [240] banded settlement; [300] agents over MCP, REST or x402; [410] the payment return rail (Stripe or x402, seller payout after the banded fee); [420] the signed-receipt rail, issued to both parties.

MCP connection (for Claude, Cursor and other MCP clients), paste into your MCP config:

{"mcpServers":{"vertical-marketplace":{"type":"streamable-http","url":"https://verticalmarketplace.ai/api/mcp"}}}

Live demonstrations of the relay: transfer, delivery, and the collaboration rail (in development). Machine contract: /openapi.json, agent card: /.well-known/agent-card.json.

Patents

Patent Pending. Filings are on file with the USPTO. Status and the notice wording are kept in one place: /patent-notice. We do not publish a filing count on this site.

Company: Vertical Marketplace LLC, a Delaware series LLC. Your counterparty is the entity named in your seller or buyer agreement.

Machine-readable version of this page: /disclosures.txt. It is also linked from /llms.txt so agents read the same disclosures humans do.