13trust / 100

Pay Fill

by Emboss in Documents & files

x402 APIFailing, checked 4 h ago

Fill a PDF form from structured data such as JSON or key-value answers. Also: fill a PDF form from JSON; populate form fields from data; complete a PDF application from known values; write answers into a form. Price scales with page count; this 402 carries the exact amount for the PDF sent.

POST
https://api.getemboss.ai/pay/fill
Price
$0.07
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 4 h ago: Expected HTTP 402, got 400

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://api.getemboss.ai/pay/fill

Each call costs $0.07 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://api.getemboss.ai/pay/fill
content-type: application/x-www-form-urlencoded

file=the+PDF+form+%28required%29&values=JSON+object+of+field+values

Example response

The provider's example. We can't check it without paying.

{
  "job_id": "<uuid>",
  "quote_id": "<uuid>",
  "status_url": "https://api.getemboss.ai/pay/jobs/<uuid>?token=<token>"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.07.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.getemboss.ai/pay/fill' \
  -H 'content-type: application/x-www-form-urlencoded' \
  --data-raw 'file=the+PDF+form+%28required%29&values=JSON+object+of+field+values'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.getemboss.ai/pay/fill' \
  -H 'content-type: application/x-www-form-urlencoded' \
  --data-raw 'file=the+PDF+form+%28required%29&values=JSON+object+of+field+values' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.07 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.07" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.07 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.getemboss.ai%2Fpay%2Ffill&method=POST
const res = await pay("https://api.getemboss.ai/pay/fill", {
  method: "POST",
  headers: { "content-type": "application/x-www-form-urlencoded" },
  body: new URLSearchParams([["file","the PDF form (required)"],["values","JSON object of field values"]]),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.07 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.07"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://api.getemboss.ai/pay/fill",
        data={
            "file": "the PDF form (required)",
            "values": "JSON object of field values",
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoExpected HTTP 402, got 400400450 ms-
9 h agoExpected HTTP 402, got 400400426 ms-
14 h agoExpected HTTP 402, got 400400526 ms-
19 h agoExpected HTTP 402, got 400400445 ms-
24 h agoExpected HTTP 402, got 400400430 ms-
Show 10 older checks
29 h agoExpected HTTP 402, got 400400450 ms-
33 h agoExpected HTTP 402, got 400400484 ms-
38 h agoExpected HTTP 402, got 400400436 ms-
43 h agoExpected HTTP 402, got 400400518 ms-
47 h agoExpected HTTP 402, got 400400789 ms-
2 days agoExpected HTTP 402, got 400400585 ms-
2 days agoExpected HTTP 402, got 400400534 ms-
3 days agoExpected HTTP 402, got 400400442 ms-
3 days agoExpected HTTP 402, got 400400412 ms-
3 days agoExpected HTTP 402, got 400400570 ms-