Use this service when you need this capability: validate supplied NFT metadata fields, URI forms, and bounded attribute records.
0.005 USDC per call
x402 V2 exact payment on Base mainnet (eip155:8453) using USDC. The HTTP 402 challenge confirms the exact requirements before an authorized payment.
POST https://signalharness.ai/api/agent/services/nft_metadata_validate/invokeValidate supplied NFT metadata fields, URI forms, and bounded attribute records.
Caller-supplied data is processed deterministically. These tools do not supply live market feeds, query blockchain RPC, host AI models, or verify that supplied history is complete. Payment remains Base USDC for every chain category.
| Field | Type | Required | Limits |
|---|---|---|---|
| nft_metadata_request | string | Required | Minimum length 2; Maximum length 65536 |
{
"nft_metadata_request": "{\"metadata\":{\"name\":\"NFT\",\"image\":\"ipfs://example\",\"attributes\":[{\"trait_type\":\"Color\",\"value\":\"Blue\"}]}}"
}{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"additionalProperties": false,
"minProperties": 1,
"maxProperties": 1,
"required": [
"nft_metadata_request"
],
"properties": {
"nft_metadata_request": {
"type": "string",
"minLength": 2,
"maxLength": 65536
}
}
}Illustrative output from the canonical adapter fixture and schema. It is not a completed paid execution or a current live observation.
{
"service_id": "nft_metadata_validate",
"evidence_scope": "caller_supplied_data",
"nft_metadata_validation": "{\"errors\":[],\"supplied_fields\":[\"attributes\",\"image\",\"name\"],\"valid\":true}",
"warnings": [
"Validation does not fetch media or authenticate the collection."
]
}{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"additionalProperties": false,
"minProperties": 4,
"maxProperties": 4,
"required": [
"service_id",
"evidence_scope",
"nft_metadata_validation",
"warnings"
],
"properties": {
"service_id": {
"type": "string",
"const": "nft_metadata_validate",
"minLength": 21,
"maxLength": 21
},
"evidence_scope": {
"type": "string",
"const": "caller_supplied_data",
"minLength": 20,
"maxLength": 20
},
"nft_metadata_validation": {
"type": "string",
"minLength": 1,
"maxLength": 65536
},
"warnings": {
"type": "array",
"minItems": 1,
"maxItems": 8,
"items": {
"type": "string",
"minLength": 1,
"maxLength": 512
}
}
}
}Timeout: 5000 ms. Full schemas are in OpenAPI.
This schema-valid request returns the canonical HTTP 402 challenge without executing the service. A payment-capable client validates the challenge, signs only with prior authority and budget, and retries the identical body.
curl -i -X POST https://signalharness.ai/api/agent/services/nft_metadata_validate/invoke \
-H "Content-Type: application/json" \
--data '{"nft_metadata_request":"{\"metadata\":{\"name\":\"NFT\",\"image\":\"ipfs://example\",\"attributes\":[{\"trait_type\":\"Color\",\"value\":\"Blue\"}]}}"}'