{"uid":"cap_8HQBh9Xnkc8CMyAdX1-rX","slug":"api-contracts-unit-label-consistency-c4bedffa","name":"Api Contracts — Unit-label consistency","description":"Compare declared request/response coordinates for each HTTP contract. UTF-8 bytes, codepoints and tokens stay distinct; no tokenizer, conversion or remote execution. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.","url":"https://www.mahastrategies.com/api/v1/verify/api-contracts/unit-label-consistency?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"contracts":{"type":"array","maxItems":32,"minItems":1},"dataClass":{"enum":["public","synthetic"],"type":"string"},"observations":{"type":"array","maxItems":32,"minItems":1},"nonpersonalMetadata":{"type":"boolean","const":true}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.012303","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.012303/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.012303","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.012303","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_SQSFJVmbTo2EbbUpy0pgd","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.012303","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Compares declared request/response coordinates in HTTP contracts to verify that UTF-8 bytes, codepoints, and tokens are kept distinct and consistently labeled throughout the contract metadata.","exampleAgentPrompt":"Can you check these API contracts for unit-label consistency — specifically make sure bytes, codepoints, and tokens are kept distinct in the request and response coordinates? The data is synthetic and nonpersonal.","exampleUseCases":[{"title":"API spec unit-label audit before release","prompt":"Before we ship this API, can you check that all the request and response coordinate declarations in these contracts keep UTF-8 bytes, codepoints, and tokens properly distinct — no conflation? The contracts are public metadata and nonpersonal."},{"title":"Detecting token-vs-byte confusion in LLM API contracts","prompt":"I have 12 HTTP contract definitions for our LLM API and I'm worried some of them mix up byte counts with token counts in the declared coordinates — can you run a unit-label consistency check on them? Data class is synthetic."},{"title":"CI pipeline contract consistency gate","prompt":"As part of our CI checks, compare these API contract request/response coordinates and flag any places where byte, codepoint, or token labels are inconsistent or conflated — all public nonpersonal metadata, up to 30 contracts."}],"resultDescription":"A report identifying which declared request/response coordinates in the supplied HTTP contracts have inconsistent or conflated unit labels, distinguishing UTF-8 bytes, codepoints, and token counts as separate entities. Results are retained for 24 hours; receipt metadata for 90 days.","failureModes":["Empty or malformed contracts array (minItems:1 not met)","More than 32 contracts or observations submitted (maxItems exceeded)","dataClass not set to 'public' or 'synthetic'","nonpersonalMetadata not explicitly set to true","Personal or non-public data submitted causing rejection","Malformed contract declarations that cannot be parsed for coordinate comparison"],"whenToPreferThis":"Choose this endpoint when you need to audit HTTP API contract metadata specifically for unit-label consistency — ensuring bytes, codepoints, and tokens are never conflated in request/response coordinate declarations. It operates fully offline with no tokenizer, conversion, or remote execution, making it suitable for sensitive-but-nonpersonal contract metadata. Prefer it over general schema validators when the specific concern is dimensional unit labeling in API specs.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-19T06:44:44.949Z","isFirstParty":false,"canonicalSlug":"api-contracts-unit-label-consistency-c4bedffa"}