x402basequality 0.60

Upload an image and JSON metadata to IPFS for 2¢ USDC via x402 on Base.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://ipfs.c402.markets/ipfs-upload

What it does

This x402-enabled endpoint accepts a multipart/form-data POST containing an image file (PNG, JPEG, WebP, or GIF) and a companion JSON metadata file, stages them, and pins the content to IPFS. Payment of $0.02 USDC is required per request, settled on the Base network using the x402 payment protocol. The endpoint returns an upload ID along with details about the staged image, metadata, and payment settlement.

The service is live and responds with a standard x402 payment challenge when no X-PAYMENT header is provided. The accepted asset is USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, paid to address 0x1C146D7746Ea31f38eD16158f9f8cd19e03b2630. The maximum payment timeout is 600 seconds. No additional documentation pages (docs, API reference, pricing) are available from the provider; all schema information comes from the x402 challenge's outputSchema.

Because the endpoint only exposes a single operation with a well-defined input/output schema, integration is straightforward for agents or applications that need to persist images and their metadata on IPFS without managing their own pinning infrastructure.

Capabilities

ipfs-uploadipfs-pinningimage-stagingmultipart-form-datax402-paymentbase-networkusdc-micropaymentjson-metadata

Use cases

  • —Uploading NFT artwork and metadata to IPFS in a single paid request
  • —Persisting user-generated images on decentralized storage from an AI agent workflow
  • —Staging image assets and structured metadata for dApps without running your own IPFS node
  • —Automating IPFS pinning as part of a content publishing pipeline

Fit

Best for

  • —Agents or apps that need quick, pay-per-use IPFS pinning without accounts or API keys
  • —NFT minting workflows that require image + metadata uploads to IPFS
  • —Developers who want a simple HTTP POST interface to IPFS with micropayment gating

Not for

  • —Bulk or high-volume file storage (2¢ per upload adds up; no batch endpoint documented)
  • —Uploading non-image files (only image/png, image/jpeg, image/webp, image/gif accepted)
  • —Retrieving or reading back pinned content (this endpoint is upload-only)

Quick start

curl -X POST https://ipfs.c402.markets/ipfs-upload \
  -H "X-PAYMENT: <x402-payment-header>" \
  -F "image=@photo.png;type=image/png" \
  -F "metadata=@meta.json;type=application/json"

Example

Response

{
  "image": {
    "size": 204800,
    "filename": "photo.png",
    "mimeType": "image/png"
  },
  "status": "staged",
  "payment": {
    "amount": "20000",
    "settlementTx": "0xabc...def"
  },
  "metadata": {
    "size": 512,
    "preview": "{\"name\":\"My Image\",\"description\":\"An example\"}",
    "filename": "meta.json"
  },
  "uploadId": "abc123-def456"
}

Endpoint

URLhttps://ipfs.c402.markets/ipfs-upload
Transporthttp
Protocolx402
Pay to0x1C146D7746Ea31f38eD16158f9f8cd19e03b2630
CurrencyUSD COIN

Quality

0.60/ 1.00

The endpoint is live with a valid 402 challenge and a detailed outputSchema covering both input and output. However, there are no documentation pages, no usage examples from the provider, and no information about rate limits, file size limits, or how to retrieve pinned content after upload. The response example is inferred from the outputSchema, not from actual observed responses.

Warnings

  • —No documentation pages found (docs, API, pricing all return 404)
  • —File size limits are not documented
  • —No information on how to retrieve or access pinned content after upload
  • —Response example is inferred from outputSchema, not from an actual response

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 19:31:42Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/kCLLJA