Crypto Analysis & Developer Tools · x402 V2

EVM Address Checksum

Use this service when you need this capability: normalize one caller-supplied EVM address to its EIP-55 checksum representation.

Price and endpoint

LivePOSTBase USDC

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/address_checksum/invoke

Purpose

Normalize one caller-supplied EVM address to its EIP-55 checksum representation.

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.

Inputs

Request fields and validation limits
FieldTypeRequiredLimits
address_checksum_requeststringRequiredMinimum length 2; Maximum length 65536

Example request body

{
  "address_checksum_request": "{\"address\":\"0x0000000000000000000000000000000000000001\"}"
}
View complete input schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "additionalProperties": false,
  "minProperties": 1,
  "maxProperties": 1,
  "required": [
    "address_checksum_request"
  ],
  "properties": {
    "address_checksum_request": {
      "type": "string",
      "minLength": 2,
      "maxLength": 65536
    }
  }
}

Realistic output shape

Illustrative output from the canonical adapter fixture and schema. It is not a completed paid execution or a current live observation.

{
  "service_id": "address_checksum",
  "evidence_scope": "caller_supplied_data",
  "checksummed_address": "{\"address\":\"0x0000000000000000000000000000000000000001\"}",
  "warnings": [
    "Checksum normalization does not prove ownership or contract identity."
  ]
}
View complete output schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "additionalProperties": false,
  "minProperties": 4,
  "maxProperties": 4,
  "required": [
    "service_id",
    "evidence_scope",
    "checksummed_address",
    "warnings"
  ],
  "properties": {
    "service_id": {
      "type": "string",
      "const": "address_checksum",
      "minLength": 16,
      "maxLength": 16
    },
    "evidence_scope": {
      "type": "string",
      "const": "caller_supplied_data",
      "minLength": 20,
      "maxLength": 20
    },
    "checksummed_address": {
      "type": "string",
      "minLength": 1,
      "maxLength": 65536
    },
    "warnings": {
      "type": "array",
      "minItems": 1,
      "maxItems": 8,
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 512
      }
    }
  }
}

Execution limits

  • MaxInputBytes: 131072
  • MaxOutputBytes: 131072
  • MaxConcurrentExecutions: 2
  • MaxArtifacts: 0
  • MaxArtifactBytes: 0
  • RateLimitPerMinute: 30
  • MaxNodes: 10000

Timeout: 5000 ms. Full schemas are in OpenAPI.

Copyable unpaid request

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/address_checksum/invoke \
  -H "Content-Type: application/json" \
  --data '{"address_checksum_request":"{\"address\":\"0x0000000000000000000000000000000000000001\"}"}'

Continue with the paid-call walkthrough →