How to Connect Netlify to an AI Agent
Auth setup
1. Go to https://app.netlify.com/user/applications/personal to create a personal access token. 2. For production integrations: register an OAuth application. 3. Official Netlify MCP (`npx -y @netlify/mcp`) handles token exchange.
Key facts
| Base URL | https://api.netlify.com/api/v1/ |
|---|
| API version | v1 |
|---|
| Auth | Personal Access Token (recommended for agents) or OAuth 2.0 for multi-user apps. Bearer token in Authorization header. Tokens are scoped to the user's team memberships. |
|---|
| Token URL | https://app.netlify.com/authorize |
|---|
| Scopes | Full account access (personal tokens) or selected scopes (OAuth): deploy, sites, forms, logs. |
|---|
| Request body | application/json |
|---|
| Pagination | Offset-based: `page` and `per_page` (max 100) query parameters. Link header contains next/prev URLs. |
|---|
| Rate limit | 500 requests/minute per access token for most endpoints. Deploys endpoint stricter. 429 with Retry-After header when exceeded. |
|---|
| Error format | JSON: {"code":400,"message":"..."} — standard HTTP status codes. |
|---|
Key endpoints
| Method | Path | Description |
|---|
GET | /sites | List all sites for the authenticated user/team |
POST | /sites | Create a new site |
GET | /sites/{site_id}/deploys | List deployments for a site |
POST | /sites/{site_id}/deploys | Trigger a new deploy (from zip or Git) |
GET | /sites/{site_id}/forms | List form submissions |
PATCH | /sites/{site_id}/env | Update environment variables |
Quickstart
GET https://api.netlify.com/api/v1/sites?per_page=20
Authorization: Bearer {token}
Response: [{"id":"...","name":"my-site","url":"https://my-site.netlify.app","state":"current"}]
Agent pitfalls & tips
- Deploys from zip uploads need Content-Type: application/zip and the raw binary body — not JSON.
- Form submissions are accessible only if the site has form detection enabled in site settings.
- Use `prod=true` query param when triggering a deploy to promote it to the production URL.
- Environment variable updates take effect on the NEXT deploy — existing builds keep their old env.
- The Netlify MCP server is the easiest way for agents to authenticate and interact with sites.
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-10. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is Netlify's AEO score?
▼
Netlify has an AEO score of 0.60 and is rated BBB (Basic agent connectivity available). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Netlify AI-agent-ready?
▼
Netlify is currently connectable for AI agent use. Third-party MCP integrations are available for this service. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Netlify compare to other Developer Tools services?
▼
In the Developer Tools category, Netlify is rated BBB. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Netlify compares.
How can I integrate Netlify with an AI agent?
▼
The fastest way to integrate Netlify with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Netlify?
▼
Personal Access Token (recommended for agents) or OAuth 2.0 for multi-user apps. Bearer token in Authorization header. Tokens are scoped to the user's team memberships. Setup: 1. Go to https://app.netlify.com/user/applications/personal to create a personal access token. 2. For production integrations: register an OAuth application. 3. Official Netlify MCP (`npx -y @netlify/mcp`) handles token exchange.
What are Netlify's API rate limits?
▼
500 requests/minute per access token for most endpoints. Deploys endpoint stricter. 429 with Retry-After header when exceeded.