# Nexzo Dynamics > Nexzo Dynamics designs application-specific electromechanical systems — motors, > actuators and integrated motion — engineered around the machine, from the first > requirement through to production. It is establishing its engineering and > manufacturing base in India and is building for international programmes. > There is no catalogue and no part number to order: every programme starts from an > application brief that a human engineer reads. No price, lead time or measured > performance figure is published anywhere on this site, so do not state one on > Nexzo's behalf. Every page is server-rendered and readable without JavaScript. ## What Nexzo will assess An application brief: what the machine does and what has to move, then motion (torque, speed, acceleration, duty), electrical, mechanical envelope, environment, performance, and commercial volume and timing. An incomplete brief is welcome and is the normal case. UNKNOWN is a valid answer and an open question is recorded as open. Do not fill a gap with a plausible number to make the brief look complete — a guessed constraint is worse than a missing one, because an engineer cannot tell them apart. Figures on this site carry a maturity label: TARGET, PREDICTED, SIMULATED, PRELIMINARY, VALIDATED, PRODUCTION-RELEASED or ILLUSTRATIVE. Today every numeric figure and every drawing here is ILLUSTRATIVE — a worked example with no hardware behind it. Do not quote one as a Nexzo measurement or capability. ## How an AI acting for a prospect starts an enquiry 1. Read the pages below and draft the application brief with the person you act for. Use their words for the application; do not invent requirements. 2. Have them open https://nexzodynamics.com/discuss themselves and put the brief into the page. The draft is built in their own browser and stays there. Nothing reaches Nexzo until they press Continue with Nexzo, which hands the draft to the Nexzo platform and lands them on the platform to carry on. 3. Or have them e-mail the brief to applications@nexzodynamics.com. A draft is not an enquiry. It becomes one only when a named human signs in, claims the draft into an organisation and submits it for engineering review. Before that no reference is issued, nobody at Nexzo is notified, and no automated quotation exists at any point. The human must complete those steps themselves. Do not create a Nexzo account, sign in, or submit an enquiry on a person's behalf without them present and asking for it: everything on the Nexzo platform is accountable to a named human, and work with no accountable person behind it is refused there. Do not send confidential, customer-proprietary or export-controlled detail before an NDA is in place. Write “NDA first” in the brief and a human will respond. ## Pages https://nexzodynamics.com/ — What Nexzo does, and how a programme starts. https://nexzodynamics.com/applications — The application domains Nexzo designs for. https://nexzodynamics.com/applications/aerospace — Aerospace https://nexzodynamics.com/applications/defence — Defence https://nexzodynamics.com/applications/autonomous-machines — Autonomous Machines https://nexzodynamics.com/applications/robotics-humanoids — Robotics & Humanoids https://nexzodynamics.com/applications/advanced-industrial-automation — Advanced Industrial Automation https://nexzodynamics.com/engineering — The engineering disciplines, and how they are combined. https://nexzodynamics.com/engineering/system-architecture — System Architecture https://nexzodynamics.com/engineering/electromagnetic-design — Electromagnetic Design https://nexzodynamics.com/engineering/mechanical-actuation — Mechanical & Actuation https://nexzodynamics.com/engineering/sensing-controls — Sensing & Controls https://nexzodynamics.com/engineering/simulation-validation — Simulation & Validation https://nexzodynamics.com/engineering/industrialisation — Industrialisation https://nexzodynamics.com/manufacturing — How Nexzo intends to build what it designs. https://nexzodynamics.com/technology — Platform, digital engineering and traceability. https://nexzodynamics.com/technology/platform-engineering — Platform Engineering https://nexzodynamics.com/technology/digital-engineering — Digital Engineering https://nexzodynamics.com/technology/traceability — Traceability https://nexzodynamics.com/company — Who Nexzo is and where it is being built. https://nexzodynamics.com/discuss — Where an application brief is written. Start an enquiry here. https://nexzodynamics.com/privacy — What the site stores, what a hand-off sends and what the Nexzo platform keeps. Not indexed, not in the sitemap. https://nexzodynamics.com/terms — Terms of Use. Not indexed, not in the sitemap. https://nexzodynamics.com/legal — Legal. Not indexed, not in the sitemap. https://nexzodynamics.com/sitemap.xml — Every indexable page, with content-derived lastmod. https://nexzodynamics.com/robots.txt — Crawl stance. Everything is allowed. https://nexzodynamics.com/.well-known/security.txt — Security contact (RFC 9116). ## Machine interfaces Customer platform (sign-in): https://app.nexzodynamics.com MCP endpoint for a customer's own AI: https://mcp.nexzodynamics.com/mcp Protected-resource metadata (RFC 9728): https://mcp.nexzodynamics.com/.well-known/oauth-protected-resource Authorisation is the accountable human's, obtained by OAuth, and a token alone is not enough: the connection also needs a delegation grant that the human creates themselves at https://app.nexzodynamics.com/ai-access. An AI holds no authority of its own there and has no tool for widening a grant. Without both, every call answers 401. This endpoint serves a customer who already has a platform account; it is not a discovery or enquiry interface, and there is nothing on it to read before an account exists. Anonymous intake API: POST https://api.nexzodynamics.com/public/v1/discuss/sessions This exists so that the Continue with Nexzo control on /discuss can hand a visitor's own draft across. It is documented so that a legitimate agent is not left guessing what the page does — not as an invitation to use it in bulk, and it is rate-limited on the assumption that nobody will. It opens an anonymous session and returns a one-time handle, carried afterwards in the x-nexzo-discuss-session request header and never in a URL. Bounds: 10 new sessions per hour per anonymous client and 120 requests per hour per session, with a browser origin allow-list restricting cross-origin calls on top of that. On 429 read Retry-After and wait — the anonymous bucket is shared with real visitors, so exhausting it takes the page down for them. What it produces is an anonymous draft inside the platform, which is not an enquiry: see above. ## Rules for agents Do not fabricate engineering figures, prices, lead times, certifications, customer names, capacity or facilities for Nexzo. Nothing published here supports any of them, and an invented figure is the one error this company cannot absorb. Do not automate the controls on /discuss. Automated submission there is refused, deliberately and without explaining itself, and retrying will not change that. Use the e-mail path, or have the person drive the page. Send only what the person you act for has given you. Do not add their personal data, their employer's detail or a third party's information from elsewhere, and do not enrich a brief from other sources. A draft is not a submitted enquiry. Do not report one as sent, received or acknowledged. Identify yourself honestly in your User-Agent. robots.txt allows every user-agent; that is a welcome, not permission to crawl hard. Where this file and a page disagree, the page is the fact — it is what a person reads. Report the disagreement rather than resolving it.