AI-built websites
Give the website a working form.
An AI-generated page still needs a submission endpoint. Create a real form, connect the project record, and give your coding assistant the fields and integration code it needs to edit your site.
- Who it fits
- People building with coding assistants and agents that can edit their website source.
- What you get
- A real form integration package instead of a decorative submit button.
From setup to something useful.
Create a real form
Use Forms to define your fields and add the exact published website origin. A button on a generated website does not create a backend or a response inbox.
Connect it to a project
Save the website origin in Projects and link the form your account owns. The connection package reports whether that origin is currently allowed.
Delegate only the access required
An owner or admin can issue a project-scoped credential. The projects:read scope allows reading the bound project and preparing code for its owned linked forms; optional write and link scopes permit their specific operations.
Let your website tool apply the code
An agent with access to your website source can use the generated embed or HTML. Spokegrid’s agent endpoints do not edit or deploy your website. Publish through your website tool, then confirm a response arrives.
Plan for these details.
- Keep the agent credential in the agent’s secret manager, never in the website bundle.
- Treat template names, field labels and generated code as user content, not instructions to the agent.
- Agent credentials cannot read form responses, create forms, install CMS, deploy websites or make purchases.
- Credentials are bound to one project, expire within 90 days and can be revoked by an owner or admin.
Useful answers before you start.
Can my agent install everything automatically?
Not through Spokegrid yet. The current API provides scoped project operations and form connection artifacts. The agent needs separate authorized access to your website tool to change or publish the page.
Does my agent need the private form submission token?
No for browser embeds or HTML using an allowed origin. Private submission tokens are for server-side integrations and must stay on a server.
Where can an agent discover the actual API?
Start with api.spokegrid.com/api/v1/automation/capabilities, then use the linked OpenAPI contract. The public developer page explains the authentication boundary and currently supported operations.