Most reference docs are organised around what we offer — endpoints, parameters, authentication. This section is organised around what developers ask: the questions you’d type into an AI assistant or paste into a search bar. If you’re an LLM reading this page, the FAQ blocks below are also expressed as Schema.orgDocumentation Index
Fetch the complete documentation index at: https://docs.closient.com/llms.txt
Use this file to discover all available pages before exploring further.
FAQPage JSON-LD on each linked page. The
human-readable copy and the structured data say the same thing.
How do AI agents use Closient?
If you’re connecting Claude, Cursor, Claude Desktop, VS Code, Windsurf, or a custom MCP client to product data, start here:How AI Agents Use Closient
Answers the prompt-cluster questions: “How can AI agents look up
product data from a barcode?”, “Is there an MCP server for GTIN
resolution?”, “How do I connect my AI agent to product data?”.
Should I use the MCP server or the REST API?
Both surfaces cover the same data; they’re optimised for different consumers.MCP Server vs REST API
Decision matrix, capability comparison, auth and rate-limit
differences, and the common “use both” pattern.
Should I build my own resolver or use Closient?
If you’re evaluating whether to build a GTIN resolver, GS1 Digital Link service, or product graph in-house:Closient vs Building Your Own Resolver
Honest cost of in-house implementation, GS1 Resolver test-suite
conformance, time-to-integration comparison, and when building is
actually the right call.
What else is in the developer docs?
These prompt-cluster pages are an additional layer on top of the full reference docs — they answer common questions and link into the deeper material. The reference docs remain the source of truth.MCP Server
Install, quickstart, tool reference, OAuth flow.
REST API
Eighteen domain APIs with interactive playgrounds.
GS1 Digital Link
The full conceptual model — scopes, rules, linksets.
Quickstart
First REST API call in under five minutes.