← Market

X402 · Lpc Nft Info

LPC Collection Facts. Collection-level facts for the LPC NFT collection on Polygon: supply, holder count, tier distribution, concentration and marketplace activity. Every response carries the scan time, so the age of the snapshot is never hidden. Aggregates only — no owner addresses, no account-linked data, and not a valuation.

POST https://app.tenna.ai/api/x402/lumi/lpc_nft_info

0.1 USDC on Base · payTo 0x7eaf3c393a8996e124c0fa7ccbc55019854c4c5b

Status: verified · payable

Operator badge: embed this endpoint's live status badge — it reads "Verified Payable" only while the probe record backs it.

Settlement: direct to the seller's payTo — 0% HIVE402 take

Payment routes

Base · 0.1 USDC · payTo 0x7eaf3c393a8996e124c0fa7ccbc55019854c4c5b · via cdp · settles direct
{
  "offering": "lpc_nft_info"
}
{
  "dataFreshness": {},
  "limitations": [
    "<limitations>"
  ],
  "observed": true,
  "offering": "lpc_nft_info",
  "provenance": {
    "auditedDeliverableHash": null,
    "generatedAt": 1,
    "ledgerLaunchCount": null,
    "ledgerSpanHours": null,
    "resultHash": null,
    "rubricVersion": null,
    "source": "<source>"
  },
  "schemaVersion": "<schemaVersion>"
}

Script Master Labs LLC · SDVOSB · Kinston, NC · Terms · Refunds · Privacy · Contact

SML network: ScriptMasterLabs — the main site · SML Dual Market — the human storefront · VA Ratings — VA disability ratings, free for veterans

Agent intel trust badge

Trust score63 / 100 · breakdown
Probe uptime (30d)100.0% over 1 probes · daily
Avg 402 latency819 ms
Paid calls (30d, on-chain)0 calls · 0 buyers
Facilitator-reported (30d)1 calls · 1 payers (CDP Bazaar)

How to call

POST https://app.tenna.ai/api/x402/lumi/lpc_nft_info · input in body · spec from live-challenge

Input schema
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "offering"
  ],
  "description": "No inputs; returns the current snapshot.",
  "properties": {
    "offering": {
      "type": "string",
      "const": "lpc_nft_info",
      "description": "Offering identifier. Must be exactly 'lpc_nft_info'."
    }
  }
}
Output schema
{
  "type": "object",
  "additionalProperties": true,
  "required": [
    "schemaVersion",
    "offering",
    "provenance",
    "limitations",
    "observed",
    "dataFreshness"
  ],
  "properties": {
    "schemaVersion": {
      "type": "string",
      "description": "Deliverable contract version."
    },
    "offering": {
      "type": "string",
      "description": "Offering that produced this result.",
      "const": "lpc_nft_info"
    },
    "provenance": {
      "type": "object",
      "description": "Reproducibility metadata so another agent can audit this.",
      "properties": {
        "source": {
          "type": "string",
          "description": "Data origin."
        },
        "generatedAt": {
          "type": "integer",
          "description": "Unix seconds."
        },
        "ledgerLaunchCount": {
          "type": [
            "integer",
            "null"
          ],
          "description": "Launches in the ledger. Null when the offering is not derived from the launch ledger — this means not applicable, not collection failure."
        },
        "ledgerSpanHours": {
          "type": [
            "number",
            "null"
          ],
          "description": "Hours of history covered. Null when the offering is not derived from the launch ledger."
        },
        "rubricVersion": {
          "type": [
            "string",
            "null"
          ],
          "description": "Rubric the verdict was produced under. Present on audit offerings."
        },
        "resultHash": {
          "type": [
            "string",
            "null"
          ],
          "description": "Hash of the audited input, so the same verdict can be reproduced. Present on audit offerings."
        },
        "auditedDeliverableHash": {
          "type": [
            "string",
            "null"
          ],
          "description": "Explicit alias for resultHash on deliverable-audit results; hashes the buyer-supplied input, not the audit envelope."
        }
      }
    },
    "limitations": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Coverage limits and missing data, always disclosed."
    },
    "chainId": {
      "type": [
        "integer",
        "null"
      ],
      "description": "Chain the contract lives on."
    },
    "contract": {
      "type": [
        "string",
        "null"
      ],
      "description": "Contract queried."
    },
    "largestTierShare": {
      "type": [
        "number",
        "null"
      ],
      "description": "Share held by the largest tier, percent."
    },
    "tokensPerHolder": {
      "type": [
        "number",
        "null"
      ],
      "description": "Overall collection totalTokens divided by distinct totalHolders."
    },
    "observed": {
      "type": "boolean",
      "description": "Whether a snapshot was available."
    },
    "totalTokens": {
      "type": [
        "integer",
        "null"
      ],
      "description": "Tokens in the collection."
    },
    "totalHolders": {
      "type": [
        "integer",
        "null"
      ],
      "description": "Distinct holding addresses."
    },
    "tiers": {
      "type": "array",
      "description": "Per-tier token and holder counts.",
      "items": {
        "type": "object"
      }
    },
    "holderCountSemantics": {
      "type": "object",
      "description": "Machine-readable populations and cross-tier counting semantics."
    },
    "marketplace": {
      "type": "object",
      "description": "Provider-marketplace counts and explicit coverage scope."
    },
    "dataFreshness": {
      "type": "object",
      "description": "Scan time, age and sync schedule. Keys without a 'sync' prefix describe the data (lastFullScanAt, ageHours, provider, snapshotFetchedAt); 'sync' keys describe the job that refreshes it. freshnessNote_en states how lastFullScanAt and syncLastRunAt differ, since they sit side by side and can be seconds apart."
    }
  }
}
curl -i -X POST 'https://app.tenna.ai/api/x402/lumi/lpc_nft_info' \
  -H 'content-type: application/json' -d '{"offering":"lpc_nft_info"}'

Agents: POST https://hive402.scriptmasterlabs.com/mcp → route_task / proxy_call · SDK /sdk/hive402.mjs

Try it (your wallet signs; HIVE402 never holds funds)