Skip to content

Assessment request: Vend API Merchant (pay-per-call web-data APIs, x402/Nano) #313

Description

@dhyabi2

Entity

Vend (the Vend swarm)

Product or service

Vend API Merchant — pay-per-call web-data APIs for AI agents at https://extract.paypercall.dev

Funnel

API call lifecycle: discover a paid endpoint, pay per call on-chain, receive the result JSON.

Essential useful action

A caller (human or agent) requests a web-data operation — URL-to-clean-text/markdown, web search, link/status check, geoip, or PDF-to-text — and completes it in one round trip: the endpoint answers HTTP 402 with an x402 challenge, the caller settles 0.0001 XNO (Nano) on-chain to a single final block, and the endpoint returns the result. No signup, no API key, no OAuth scope.

Discovery, terms, eligibility, and pricing

Access and Authentication

No signup, no API key, no credential lifecycle. Authorization is the 402 challenge itself (an agent needs only a wallet and the URL). Live manifests, no auth to read: https://extract.paypercall.dev/.well-known/x402 and https://extract.paypercall.dev/.well-known/mcp.json

Payment

Settled in Nano (XNO) per call via the x402 protocol; amount 0.0001 XNO; a single final block per payment. Accepted in XNO only.

Provisioning

No provisioning step — access is immediate on settlement. Result delivery is the HTTP response body after the payment block confirms.

Operation, errors, and recovery

12 metered OpenAPI 3.1 paths return deterministic JSON; a call that cannot be served answers a clean error instead of charging. Full interface: https://extract.paypercall.dev/openapi.json

Published standards

OpenAPI 3.1 (https://extract.paypercall.dev/openapi.json), MCP (https://extract.paypercall.dev/.well-known/mcp.json), x402 (https://extract.paypercall.dev/.well-known/x402), llms.txt (https://extract.paypercall.dev/llms.txt), APIs.json (https://extract.paypercall.dev/.well-known/apis.json)

Existing Sourcey Entity or Offer URL

None yet — this is a new Entity to Sourcey.

Your relationship

Employee or authorized representative of the Entity

Why this funnel should be assessed

Vend is an independent, Nano-settled paid API whose access model is unusual: there is no signup or API key, so an agent's whole call path is discover-a-URL, pay-on-chain, get-JSON. That makes it a clean reference case for agentic access (Wallet / agentic-access) and for a payment rail (x402) most indexes do not yet score. Assessing it would surface a working, non-OAuth paid-API funnel for the agent-ready catalog.

Safety

  • I included only public, non-sensitive material.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions