{"uid":"cap_HOSMniBzq9Usos0in0NsR","slug":"validate-avro-avsc-5f9a98e9","name":"Validate Avro Avsc","description":"Validate Avro Avsc: Validate a JSON document for Avro Avsc. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one JSON document validation.","url":"https://market.datapackvibe.com/x402/assistant-schema-avro-avsc-59b2c7f4-validate?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"document":{"default":{},"description":"JSON value to validate; maximum 100 KB, 32 levels."}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","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.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_VKvq80Qfmp7e7dFdsXL9_","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Validates a JSON document against the Avro AVSC schema specification using a pinned SchemaStore definition, reporting JSON pointer paths and rule violations.","exampleAgentPrompt":"Can you validate this Avro AVSC JSON document for me and tell me if there are any schema violations or JSON pointer errors? Here's the document: {\"type\": \"record\", \"name\": \"User\", \"fields\": [{\"name\": \"id\", \"type\": \"int\"}]}","exampleUseCases":[{"title":"CI pipeline Avro schema check","prompt":"Before we merge this PR, validate this Avro AVSC JSON to make sure it's spec-compliant and report any JSON pointer violations: {\"type\": \"record\", \"name\": \"Order\", \"namespace\": \"com.example\", \"fields\": [{\"name\": \"orderId\", \"type\": \"string\"}]}"},{"title":"Debug malformed Avro schema","prompt":"I'm getting errors with my Avro schema and I can't figure out what's wrong — can you run this JSON through the Avro AVSC validator and show me exactly which fields are violating the spec? The document is: {\"type\": \"record\", \"fields\": [{\"name\": \"price\", \"type\": \"decimal\"}]}"},{"title":"Pre-publish Avro schema compliance audit","prompt":"I want to publish this Avro AVSC schema to our data catalog but first I need to confirm it passes SchemaStore validation — please check it and list any rule violations with their JSON pointers: {\"type\": \"record\", \"name\": \"Event\", \"namespace\": \"com.events\", \"doc\": \"An event record\", \"fields\": [{\"name\": \"eventId\", \"type\": \"string\"}, {\"name\": \"timestamp\", \"type\": \"long\"}]}"}],"resultDescription":"Returns a validation outcome for the submitted JSON document against the Avro AVSC SchemaStore definition, including a list of JSON pointer paths that fail validation and descriptions of the specific rule violations found. If the document is valid, indicates successful compliance.","failureModes":["Document exceeds 100 KB size limit — rejected with size error","JSON nesting exceeds 32 levels — rejected","Malformed JSON submitted (not parseable) — parse error returned","Schema definition unavailable or pinned version mismatch — validation may be incomplete","Empty or null document submitted — validation error returned"],"whenToPreferThis":"Choose this endpoint when you need deterministic, spec-pinned validation of an Avro AVSC JSON document against the official SchemaStore definition, especially when you require precise JSON pointer–level error reporting. It is ideal for CI/CD pipelines, pre-publish compliance checks, or debugging Avro schemas up to 100 KB. Prefer it over generic JSON validators because it uses a pinned Avro-specific schema definition rather than a generic or ad-hoc rule set.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-29T07:45:44.101Z","isFirstParty":false,"canonicalSlug":"validate-avro-avsc-5f9a98e9"}