{"name":"Endstate API","url":"https://docs.endstate.io/","version":"1.0.0","protocolVersion":"0.3","preferredTransport":"HTTP+JSON","supportedInterfaces":[{"url":"https://docs.endstate.io/","protocolBinding":"HTTP+JSON","protocolVersion":"0.3"}],"provider":{"url":"https://docs.endstate.io/","organization":"Endstate API"},"documentationUrl":"https://docs.endstate.io/","capabilities":{"streaming":false,"pushNotifications":false},"defaultInputModes":["text/plain"],"defaultOutputModes":["text/plain"],"skills":[{"id":"provision-catalog","name":"endstate-provision-catalog","description":"Use when setting up or registering physical products in Endstate so they can later be verified - creating a collection, creating a unit for each item, and pairing an NFC chip (real or test) to each unit. This is the back-office/fulfillment setup side; for the customer-facing tap-to-verify flow, use the verify-experience skill instead.","tags":[],"url":"https://docs.endstate.io/.well-known/agent-skills/provision-catalog/skill.md"},{"id":"verify-experience","name":"endstate-verify-experience","description":"Use when building a product-verification experience with the Endstate API - letting a user tap an NFC chip on a physical item, in a web or mobile frontend, and confirming whether the item is authentic. Covers the frontend tap capture, verification either server-side or directly from the browser with a publishable key, the session-token handoff, optional ownership transfer (claiming via the Endstate relay), credential rules, and error handling.","tags":[],"url":"https://docs.endstate.io/.well-known/agent-skills/verify-experience/skill.md"}]}