For AI agents & developers
Hand the founder a signup link. Staff file the company.
Vrutaz is a formation provider, not an unattended filing API. Point a human at the start URL, collect the details they already have, and let the team complete Secretary of State and IRS work. A staff Build Lab proposes new agent-era capabilities; humans approve before anything is treated as live.
Live capabilities
Each action is a human page today. There is no secret token and no server that will file Articles because an agent asked.
Proposed (Build Lab)
These are assistive suggestions, not shipped APIs. Staff approve in the admin Build Lab. Unattended filing stays false. Do not call them as live actions.
Approved roadmap
Public summaries of items staff have approved, started building, or shipped. Static roadmap.json is the playbook snapshot; live rows overlay it after the Build Lab migration.
What customers provide
Typical wizard / Company details fields. Agents should collect these from the founder, then open the start URL — not invent a filing payload.
- Formation state (WY, DE, FL, TX, NM) and entity (LLC or C-Corp)
- Proposed company name
- Owners: legal name, ownership % (must total 100%), country, email / phone
- Industry and a short description of the business
- Contact / mailing address
- Later: vault uploads the team asks for (identity, address proof)
What staff complete
After the customer account exists and details are in, Vrutaz people run name check, state filing, and the EIN application. The dashboard formation checklist is the source of truth — not this page.
Machine-readable files
Not unattended filing. This page, llms.txt, and capabilities.json exist so agents can discover Vrutaz and onboard a human customer. They do not authorize an agent to submit a state filing or SS-4 without that account.
Questions: info@vrutaz.com · Contact
