Developer and AI agent resources
TeneX Studio publishes a documented machine interface: standard files, markdown negotiation and structured data. This page lists everything a developer or an AI agent can read on tenex.studio.
Standard files
The site exposes the usual discovery files, at predictable URLs.
llms.txt: the offer, the pages, the proof and a usage guide for agents
XML sitemap with FR/EN hreflang
Markdown negotiation
Key pages serve a markdown version of their content. Send the Accept: text/markdown header and the response comes back as text/markdown with Vary: Accept.
Example: curl -H "Accept: text/markdown" https://tenex.studio/en/
Direct URLs also work, by appending .md to the path.
Every journal article exists in markdown: /blog/<slug>.md and /en/blog/<slug>.md.
Nonexistent paths return a real HTTP 404 status, with a markdown body listing where to look.
Structured data
Every page ships schema.org JSON-LD: ProfessionalService, WebSite, Person, FAQPage, BlogPosting, Offer, Service, BreadcrumbList depending on the page.
Content is fully server-rendered: headings, copy and FAQs are readable without JavaScript.
No public API
TeneX Studio is an agency, not a software product: there is no public API, no webhooks, no MCP server. The machine interface is the files and pages above.
For a project or an integration, the most direct route is a conversation.