Image Metadata API
Reads an image's EXIF/ICC/IPTC/XMP metadata and can return a copy with all metadata stripped.
Agents read this page asGET /v1/image-metadata/schemafree: schema, examples, errors, price
- Endpoint
- POST /v1/image-metadata
- Price
- $0.003 per call
- Timeout
- 30 s
- max_timeout_seconds
- 51 (the whole call as the 402 envelope sells it: the timeout, plus payment verification and settlement around it)
- Response cap
- 25 MB (26,214,400 bytes)
- Family
- Images
When to use it
Reading and stripping image metadata safely needs a real decoder and a hardened fetch: an agent that pulls the URL itself walks past every SSRF control, and a strip must be byte-reproducible, which an ad-hoc re-encode is not.
When not to use it
- The input is over 25 MB (26,214,400 bytes): image-metadata answers too_large (413).
- The destination needs more than 30 s to answer: the call ends with upstream_timeout (424).
- The destination is on a private or local network: the network guard refuses it with blocked_target (403).
Parameters
One JSON body. The schema is free at GET /v1/image-metadata/schema.
| Field | Type | Required | Description |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the image to inspect, up to 2048 characters; redirects are followed and the format is detected from the bytes. |
| strip | boolean | no | When true, also return a same-format copy re-encoded with every metadata block removed (lossy sources at quality 80); allowed for JPEG, PNG, WebP, TIFF and GIF. Default: false. |
Limits
| Limit | Value |
|---|---|
| Size cap | 25 MB (26,214,400 bytes) |
| Timeout | 30 s |
Show the JSON Schema the handler validates against
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"format": "uri",
"description": "Absolute http(s) URL of the image to inspect, up to 2048 characters; redirects are followed and the format is detected from the bytes."
},
"strip": {
"default": false,
"description": "When true, also return a same-format copy re-encoded with every metadata block removed (lossy sources at quality 80); allowed for JPEG, PNG, WebP, TIFF and GIF.",
"type": "boolean"
}
},
"required": [
"url"
],
"additionalProperties": false
}Example
The published example, verbatim: the request and the response it returns.
POST /v1/image-metadata
content-type: application/json
payment-signature: <base64 x402 payload>
{
"url": "https://grist.tools/samples/images/metadata-exif.jpg",
"strip": true
}Without the payment-signature header the call answers 402 with the payment requirements, including this endpoint's price and its max_timeout_seconds, so the deadline is known before anything is paid. The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case we cannot state for you is a settlement call that fails without answering: the error message says so when that is what happened.
200 OK
payment-response: <base64 settlement receipt>
{
"source_url": "https://grist.tools/samples/images/metadata-exif.jpg",
"format": "jpeg",
"width": 32,
"height": 24,
"channels": 3,
"space": "srgb",
"depth": "uchar",
"has_alpha": false,
"has_profile": true,
"orientation": 6,
"density": 72,
"is_progressive": false,
"metadata": {
"exif_bytes": 186,
"icc_bytes": 480,
"iptc_bytes": null,
"xmp_bytes": null
},
"bytes": 1024,
"stripped": {
"format": "jpeg",
"bytes": 333,
"image_base64": "/9j/2wBDAAYEBQYFBAYGBQYHBwYIChAKCgkJChQODwwQFxQYGBcUFhYaHSUfGhsj..."
}
}Sample file: images/metadata-exif.jpg. 32x24 two-tone JPEG carrying an EXIF block (orientation 6, 72 dpi) and an embedded sRGB ICC profile, built with sharp from raw pixels.
In the sample itself, the segments before the first scan run APP1, APP2, DQT, DQT, SOF0, DHT, DHT, DHT, DHT and SOS, and the baseline frame header declares 32 by 24 pixels, 8-bit precision and 3 components.
Response fields
| Field | Type | In the example |
|---|---|---|
| source_url | string | "https://grist.tools/samples/images/metadata-exif.jpg" |
| format | string | "jpeg" |
| width | number | 32 |
| height | number | 24 |
| channels | number | 3 |
| space | string | "srgb" |
| depth | string | "uchar" |
| has_alpha | boolean | false |
| has_profile | boolean | true |
| orientation | number | 6 |
| density | number | 72 |
| is_progressive | boolean | false |
| metadata | object | an object with exif_bytes, icc_bytes, iptc_bytes and xmp_bytes |
| bytes | number | 1024 |
| stripped | object | an object with format, bytes and image_base64 |
Deterministic: the same input returns the same output. Clock-derived fields, when present, are declared in the response.
Call it from code
The client reads the 402, signs the payment and retries on its own.
// image-metadata: $0.003 per call, paid in USD Coin on eip155:8453 via x402
// Install: npm install @x402/fetch@2 @x402/evm@2 viem@2
// Save as client.mjs (ES module, Node 18+), export EVM_PRIVATE_KEY with the paying wallet's key in your shell, then run: node client.mjs
// The wrapper reads the 402 (payment-required), signs and retries with payment-signature.
import { wrapFetchWithPayment, x402Client, decodePaymentResponseHeader } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm/exact/client'
import { privateKeyToAccount } from 'viem/accounts'
const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY)
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(account))
const fetchWithPayment = wrapFetchWithPayment(fetch, client)
const body = {
"url": "https://grist.tools/samples/images/metadata-exif.jpg",
"strip": true
}
const res = await fetchWithPayment('https://grist.tools/v1/image-metadata', {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify(body),
})
console.log(res.status, await res.json())
const settle = res.headers.get('payment-response')
if (settle) console.log(decodePaymentResponseHeader(settle).transaction)# image-metadata: $0.003 per call, paid in USD Coin on eip155:8453 via x402
# Install: pip install "x402[requests,evm]>=2.24,<3"
# The session reads the 402 (payment-required), signs and retries with payment-signature.
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http import decode_payment_response_header
from x402.http.clients.requests import x402_requests
from x402.mechanisms.evm.exact import register_exact_evm_client
from x402.mechanisms.evm.signers import EthAccountSigner
account = Account.from_key(os.environ["EVM_PRIVATE_KEY"])
client = x402ClientSync()
register_exact_evm_client(client, EthAccountSigner(account), networks="eip155:8453")
session = x402_requests(client)
payload = {
"url": "https://grist.tools/samples/images/metadata-exif.jpg",
"strip": True
}
res = session.post("https://grist.tools/v1/image-metadata", json=payload)
print(res.status_code, res.json())
settle = res.headers.get("payment-response")
if settle:
print(decode_payment_response_header(settle).transaction)# image-metadata: $0.003 per call, paid in USD Coin on eip155:8453 via x402
# 1. Unpaid call: HTTP 402, the requirements in the payment-required header (base64 JSON) and in the body.
curl -i -X POST 'https://grist.tools/v1/image-metadata' -H 'content-type: application/json' -d '{"url":"https://grist.tools/samples/images/metadata-exif.jpg","strip":true}'
# 2. Same call with the signed payment (an EIP-3009 authorization, EIP-712 signed: it cannot be
# typed by hand). x-payment is accepted as the v1 alternative. HTTP 200 carries payment-response.
curl -i -X POST 'https://grist.tools/v1/image-metadata' -H 'content-type: application/json' -H 'payment-signature: <base64 x402 payload>' -d '{"url":"https://grist.tools/samples/images/metadata-exif.jpg","strip":true}'Errors
Every error is typed JSON. Only a successful call is settled.
| Code | HTTP | When |
|---|---|---|
| invalid_input | 400 | The body does not match the schema on this page. Nothing is charged. The body does not match the schema; its fields are url and strip. |
| blocked_target | 403 | The destination is refused by the network guard: a disallowed address, or, for HTTP requests, a scheme other than http/https, a port other than 80/443, or credentials in the URL. |
| unreachable_target | 424 | The destination you named did not resolve or refused the connection. |
| upstream_timeout | 424 | The destination you named did not answer before the declared timeout for this endpoint expired. |
| unsupported_content_type | 415 | The destination returned a type this endpoint does not handle. |
| too_large | 413 | The response exceeded the size cap while streaming, or decompressed at more than the allowed ratio. |
| unprocessable | 422 | The bytes arrived but could not be processed, for instance a malformed document. |
| internal | 500 | Our fault, and in almost every case nothing is charged. The exceptions come after the call has run and the settlement call was made: the message "The work was done but settlement could not be completed", and the messages starting with "Payment settlement returned". There, whether the payment moved is unknown to us as well. The payment moves at most once: its nonce is single-use and settlement is idempotent, so a retry with it is never charged twice. A retry is normally refused with a 402: replay_consumed, an expiry reason, or a reason saying the nonce was already used once the transfer is on-chain. Only if our server restarted before the transfer was final can a retry run the call again. Even then, the payment moves at most once. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain; to call again, sign a new payment. |
| rate_limited | 429 | Too many calls from the same payer, or too many calls towards the same destination domain. Nothing is charged. |
| concurrency_limit, registry_at_capacity, upstream_unavailable | 503 | We could not serve the call right now. Retryable: wait the number of seconds in the retry-after header, then repeat the call. concurrency_limit and registry_at_capacity mean we were at capacity: the call did not run. You can send the same payment again if its validBefore is still far enough away to cover another call. If it is not, the retry gets a 402 authorization_validity_too_short: sign a new payment. upstream_unavailable means our internal service failed or did not answer in time: the call may already have run and the payment may have been settled. A retry with the same payment can get a 402 whose error field says why. authorization_validity_too_short: too little time is left before validBefore to cover another call. This check comes before the replay check, so it does not tell whether the first payment was settled. replay_consumed (the payment was used and may have been settled) or replay_exhausted (too many attempts): sign a new payment. replay_in_flight: the first call is still running, so wait and do not pay again. invalid_exact_evm_nonce_already_used: the transfer is already on-chain, so this payment cannot move again. Sign a new payment. An authorization can be settled only once, since its nonce is single-use. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain. |
| misconfigured | 503 | The service is not configured to serve calls. The call did not run and nothing is charged. It needs a fix on our side, so there is no retry delay to wait for. |
Input that is rejected before the tool runs (malformed JSON, schema mismatch, body over the size limit) is never charged.
Questions
How much does a call to the Image Metadata API cost?
$0.003 per call, paid in USD Coin on Base via x402. There is no account and no API key: the price is in the 402 answer, before anything is paid.
What is the timeout of image-metadata?
The endpoint itself runs for at most 30 s. max_timeout_seconds in the 402 answer is 51: that covers the whole call, including payment verification and settlement around it.
How large can a response from image-metadata be?
The response-size cap is 25 MB (26,214,400 bytes).
Is the image-metadata input schema free to read?
Yes. GET https://grist.tools/v1/image-metadata/schema returns the input schema for free, paid endpoints included.
What happens if a call to image-metadata fails?
The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case that cannot be stated in advance is a settlement call that fails without answering: the error message says so when that is what happened.
What does image-metadata return?
A JSON object with 15 top-level fields: source_url, format, width, height, channels, space, depth, has_alpha, has_profile, orientation, density, is_progressive, metadata, bytes and stripped. The example on this page is a real call over images/metadata-exif.jpg.