Assay

ipfs-pay-to-pin-mainnet-c55e3346b752.herokuapp.com

Infra & storage2 endpointsipfs-pay-to-pin-mainnet-c55e3346b752.herokuapp.com

Upload one file as a Base64-encoded JSON payload

Pays to ZJEC6JMCNYZFJUQIA4KRVXPTU34F2UQCRZEB5BX5ZS57CPVKTUFK3WA5IY

Broken2 of 2 failing · 20h ago
$0.010328
USDC
Score
None yetno buyer reviews yet
Positive
None yetno buyer reviews yet
Paid calls
341 distinct payer
Verified
20h ago0 of 2 as listed
On-chain
ZJEC6JMC…3WA5IYpayout address on Algorand
All2With a finding2

2 of 2 endpoints

  • POST

    /api/v1/pin

    Upload one file as a Base64-encoded JSON payload

    Rejected the call20h agoipfs-pay-to-pin-mainnet-c55e3346b752.herokuapp.com

    $0.010328
    per call, USDC
    Try it
  • POST

    /api/v1/pin

    Upload one file as a Base64-encoded JSON payload; on successful payment, the service pins it to IPFS and returns cid, ipfs_cid, and gateway_url.

    Rejected the call20h agoipfs-pay-to-pin-mainnet-c55e3346b752.herokuapp.com

    $0.010328
    per call, USDC
    Open below

    Call it from here

    POST /api/v1/pin

    Assay builds the request this listing describes, sends it, and shows you exactly what comes back — including when what comes back is a complaint.

    The request, built from the listing

    POST https://ipfs-pay-to-pin-mainnet-c55e3346b752.herokuapp.com/api/v1/pin

{"data":"base64_encoded_string_here...","filename":"example.png"}

    Declared inputsdatafilename

    Listed at $0.010328. If it demands payment, you will see its live terms — this site cannot settle them.

    This page holds no key and cannot move money. Paid verification runs in an isolated worker with the only signing account, under the spend ceiling published in the methodology.

Buyer reviews

none yet · a review costs a settlement

Nobody has bought from ipfs-pay-to-pin-mainnet-c55e3346b752.herokuapp.com through an address that came back to write about it. Rather than print an empty box, this page hands the position to the evidence it does have — Assay’s own verification record, immediately below.

  1. 01

    Pay the merchant

    Call one of their endpoints and settle the 402 challenge in USDC on Algorand mainnet. That transfer is the whole credential.

  2. 02

    Sign the settlement

    Connect the address that sent it and sign a message naming this merchant, that transaction and your score. Assay stores no account and no password.

  3. 03

    The receipt travels with it

    Your review renders with its transaction id linked to the public explorer, so anyone can re-derive that you were a customer. One settlement buys one review.

Assay’s own prober is barred from reviewing, and the exclusion is a row in the database rather than a claim in a footer. Own this payout address? Claim the listing

Verification record

last sweep 20h ago · 2 of 2 covered

Nobody has reviewed ipfs-pay-to-pin-mainnet-c55e3346b752.herokuapp.com yet — a review attaches to a payout address and opens once a buyer has settled with it, because a settlement is the only thing that proves a reviewer was a customer. Until then this is the evidence Assay has: calls it made itself, and what came back.

What the last sweep found

answered, but not as listed
2 answered, but not as listed
  • Rejected the call2 endpoints
    • /api/v1/pin
    • /api/v1/pin

List every endpoint with a finding · checked 20h ago

Settled payments

Assay has not paid this merchant yet. Paid probing rotates across the catalogue under a published spend ceiling, so an endpoint without a receipt is one we have not bought from — not one that failed.