Agent Documentation
Robotico is designed to be readable by people, search crawlers, and MCP-capable agents. Use this page as the operating guide for discovery, markdown retrieval, citation, and safe data maintenance.
Start Here
| Need | Use |
|---|---|
| Find public pages | /llms.txt, /llms-full.txt, and /sitemap.xml |
| Fetch markdown for a page | Send Accept: text/markdown to the page, or call https://robotico.market/api/markdown?path=/docs/agents |
| Use structured tools | MCP developer docs |
| Discover MCP metadata | server.json and server-card.json |
| Discover agent skills | agent-skills index |
Agent Rules
- Prefer canonical Robotico URLs when citing facts.
- Use markdown retrieval for page summaries and MCP tools for structured reads or writes.
- Do not infer entity IDs from names. Resolve companies and robots through search or canonical URLs.
- Read existing records before writing. For robots, keep
get_robotlightweight unless evidence is needed. - Attach evidence close to the fact it supports. Use dot paths such as
tagline,status, orspecifications.height. - Stage risky robot changes for review instead of directly mutating public profiles.
- Run duplicate checks before creating timeline events.
- Use audit-log tools when a user asks what changed, who changed it, or why a value moved.
Markdown Access
Public pages can return markdown for agents. Use this when the task is summarization, citation, retrieval, or context gathering.
curl -H "Accept: text/markdown" https://robotico.market/companies
curl "https://robotico.market/api/markdown?path=/humanoids"
curl "https://robotico.market/api/markdown?path=/docs/agents"High-value markdown targets include company pages, robot/product pages, news articles, people profiles, investor profiles, contributor profiles, and these public docs pages.
MCP Access
Use MCP when an agent needs exact schemas, structured JSON, authenticated writes, evidence operations, audit logs, or timeline duplicate checks. Add the hosted endpoint by URL with no token. The client discovers Robotico OAuth 2.1 and opens a browser for approval; headless clients can use the device authorization flow.
{
"mcpServers": {
"robotico": {
"url": "https://robotico.market/mcp"
}
}
}Existing rbt_ developer bearer tokens remain supported during the deprecation window as a legacy fallback. New connections should use OAuth 2.1. After mounting the MCP server, call ping and tools/list. Tool schemas are the live contract. Connection details are documented in MCP developer docs.
Citation Guidance
- Cite Robotico entity pages for company, robot, person, investor, and contributor facts.
- Cite Robotico article pages for editorial claims and analysis.
- Use field evidence or timeline sources when a user asks for primary-source support.
- When Robotico data conflicts with an external source, surface the conflict instead of silently choosing one.
Public vs Authenticated Work
| Work type | Access model |
|---|---|
| Page reads and markdown retrieval | Public |
| MCP public reads | OAuth-connected, active, email-verified account |
| Company and robot writes | Company representative or admin through the same OAuth connection |
| Article publishing | Contributor, verified contributor, or admin through the same OAuth connection |
| Event review and candidate publishing | Reviewer or admin through the same OAuth connection |