Agent Hub
Developer Hub
Discovery & Documentation
Seven discovery endpoints, standards-compliant protocols, and everything an agent needs to find and interact with BoxNCase programmatically.
Discovery Endpoints
Quick Start
Connect via MCP
# Claude Desktop / any MCP client npx mcp-remote https://www.boxncase.com/mcp/mcp # Verify connection curl https://www.boxncase.com/.well-known/mcp/server-card.json
Search Products (REST)
curl "https://www.boxncase.com/api/search?q=truffle+oil&hitsPerPage=5"
Request Markdown
curl -H "Accept: text/markdown" https://www.boxncase.com/products/valrhona-dark-chocolate
Discover APIs
# API catalog curl https://www.boxncase.com/.well-known/api-catalog # Agent skills curl https://www.boxncase.com/.well-known/agent-skills/index.json # Link headers (homepage) curl -I https://www.boxncase.com/ | grep Link
Homepage Link Headers
The homepage returns RFC 8288 Link headers for automatic agent discovery:
Link: </.well-known/api-catalog>; rel="api-catalog",
</.well-known/agent-skills/index.json>; rel="describedby",
</llms.txt>; rel="service-doc"; type="text/plain"Content Signals
AI Content Usage Preferences
Declared via Content-Signal directive in robots.txt (IETF draft-romm-aipref-contentsignals):
# robots.txt
Content-Signal: ai-train=no, search=yes, ai-input=yes
Content-Signal: ai-train=no, search=yes, ai-input=yes
ai-train = no
Do not use for model training
search = yes
Index for search results
ai-input = yes
May use as grounded AI context