Support status
No mailbox published yetA monitored address is posted on /contact when one opens
How can we help?
CORPORE is an open-source platform for 3D AI agents, and this domain serves it as a static site. There is no account system and no application server behind it: every request under /api/* on this deployment returns 404. No contact mailbox is published yet either. /contact is the route map: it records what each kind of report covers and what to include, so a report is actionable the day an address opens.
Where things go
Four surfaces that answer today. Two of them are documentation, two are the contact route map.
Contact
/contact
The route map for copyright and takedown, abuse, privacy and data requests, security, legal notices, and product problems. Each route lists what a report needs to carry.
Security
/contact
Report a vulnerability in this site or in one of the tools it ships. Please do not post anything exploitable in public, and include steps to reproduce and what an attacker gains.
Docs
/docs
Embed guides, SDK quickstarts, and the API reference, all served as static pages. Most "how do I" questions are answered here before they become a report.
MCP tool catalog
/mcp-tools
Every MCP tool this project publishes, what it does, and which server hosts it. Generated from source, so it matches the code rather than a description of it.
Routes on the contact page
Each of these is documented at /contact with the detail it needs to be acted on.
What to expect
CORPORE is an open-source project supported by its maintainers on a best-effort basis.
Languages
English
Cost
FreeSupport is not a paid product
Before you reach out
Two of these catch most reports before they are written.
1
Check whether the page you used is server-backed
This deployment is static. Nothing under /api/* is served from this domain, so a page or button that calls one of those routes will fail here even though the markup is intact. Say which page you were on and that is usually enough to place the failure.
2
Check the docs and the tool catalog
The written reference lives at /docs, and every published MCP tool is listed at /mcp-tools with what it does and which server hosts it.
3
Include the details that make it reproducible
The page URL, what you expected, what happened instead, and your browser and OS. For anything payment related, the public transaction signature helps and no secret ever does.
What to include in a bug report
The more of this you give us up front, the faster we can reproduce.
- The page URL and the exact action that failed, including any button or form involved.
- What you expected and what happened instead, with the full error text if the browser or an assistant printed one.
- Your browser and OS, and the version of anything you installed for the report.
- Redact secrets. Never paste an API key, private key, or wallet seed. A truncated public address is fine, and a public transaction signature is better.
What this deployment actually runs
The static surfaces people write in about, and what each one is.
Open source, Apache-2.0
The viewer, the agent runtime, and the embed component
The <agent-3d> web component drops a 3D agent into any page, and the 3D Studio connector exposes tools that generate, rig, animate, inspect, and place models in AR over MCP. The docs at /docs describe each surface, and /mcp-tools is the generated catalog of the published tools. The parts of the product that needed a backend are the parts that do not answer on this deployment; the pages and the documentation are all served.