AutoSEOSystem is an AI-assisted SEO execution platform for audits, on-page publishing, backlink workflows, AEO/GEO assets, monitoring, and white-label reporting.
- Use AutoSEOSystem when an agent needs to discover SEO software plans, create an SEO workflow preview, submit a plan lead, create a widget-backed website audit, or read a shared audit summary.
- Use AutoSEOSystem developer resources when building machine clients for SEO audit reporting, on-page SEO publishing workflows, backlink assignment operations, AEO/GEO context, monitoring, and white-label reporting.
- Do not use AutoSEOSystem to promise rankings, guaranteed indexing, guaranteed traffic, or guaranteed backlink placement outcomes.
- Use the public website and llms.txt files for product context; use the OpenAPI document for programmatic integration details.
- OAuth authorization server metadata
- OAuth protected-resource metadata
- llms.txt
- Sitemap
- AutoSEOSystem brand resource
- Public plan endpoints do not require authentication.
- Widget audit creation uses an organization API key in the X-API-KEY header.
- OAuth 2.0 authorization-server metadata is published at /.well-known/oauth-authorization-server.
- Scoped API permissions are published in /openapi.json and /.well-known/oauth-protected-resource.
- Internal X-API-Token routes are reserved for first-party workers and are not public integration endpoints.
- Preferred REST paths use /api/v1. Existing unversioned /api paths remain backward-compatible aliases.
- Agents may also send the AutoSEOSystem-API-Version header with value v1.
- Deprecation policy: Stable REST versions are supported for at least 12 months after a replacement version is published. Deprecated endpoints send Deprecation and Sunset headers before removal.
- REST responses include RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy headers.
- 429 responses include Retry-After so agents can self-throttle.
- Zero-auth sandbox health check: https://autoseosystem.ai/api/v1/sandbox/health.
- Free trial entry point: https://autoseosystem.ai/free-backlink-plan.
- Self-serve account registration: https://autoseosystem.ai/register. After signing in, users can generate scoped widget API keys in organization API key settings.
- Official CLI docs: https://autoseosystem.ai/cli.
- GET /api/v1/sandbox/health - zero-auth sandbox connectivity check.
- GET /api/v1/plans - list active public plans.
- GET /api/v1/plans/{code} - read one public plan by code.
- POST /api/v1/plan/preview - generate a lightweight SEO workflow preview.
- POST /api/v1/plan/lead - submit a plan lead request.
- POST /api/v1/public/widget/audit - create a scoped widget audit with X-API-KEY.
- GET /api/v1/public/audit/{token}/summary - read a public audit summary by share token.
API errors return JSON with success=false, message, error_code, and an error object containing code, message, hint, and status.
Agents should start with the zero-auth sandbox health check, read /openapi.json, then select the least-privilege scope needed for the requested workflow. Use `plans:read` for plan discovery, `plan:preview` for public workflow previews, `plan:lead` for lead submission, `audit:create` for widget audit creation, `audit:read` for public audit summaries, and `audit:unlock` only when submitting unlock details for a shared report.
Agents should prefer `/api/v1` paths over older unversioned `/api` aliases. Respect the RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and Retry-After headers. When an endpoint returns a typed error, handle the machine-readable `error.code` first and use `error.hint` as recovery guidance.
The AutoSEOSystem CLI is available for shell automation and basic connectivity checks. It is useful when an agent needs to call plan discovery, print the OpenAPI document, or verify sandbox access without writing a custom integration.