Project API (Cursor and agents)
Read-only access to the data of a single project with a Bearer token — for SEO/AEO work in a separate Cursor project.
Each project can have one active API token. The token gives read-only access to the data for that project — it does not run checks or change settings.
- 1Open the project Settings
The “Project API” panel is near sharing.
- 2Generate a token
Copy it immediately — it is shown only once. The old token stops working.
- 3Put it in the client Cursor project
For example an env variable WRS_SEO_TOKEN or .env (do not commit it to a public repo).
- 4Call the snapshot
GET https://seo.wrs.bg/api/v1/snapshot with the header Authorization: Bearer wrs_p_…
- /api/v1/project
- Summary: rankings, forecast, visibility, GSC clicks, AI and audit score.
- /api/v1/rankings
- Keywords: volume, mobile/desktop position, forecast, ranking URL, SERP features, AI columns.
- /api/v1/audit
- The latest Website Audit + pages with issues (?limit=200).
- /api/v1/ai
- AI Tracker statuses (cited / mentioned / missing) by engine.
- /api/v1/traffic
- GSC clicks/impressions (28 days) and traffic forecast.
- /api/v1/snapshot
- Everything together — convenient for a single file in .seo_audit/wrs-snapshot.json.
Questions & answers
Can one token cover all projects?
No. The token is per project — each site has its own. That way the agent for victoria-gold.hu does not see other clients.
Does the API run paid checks?
No. It only reads data that has already been collected.
Where should I keep the token in Cursor?
In .env or a user/project secret, not in git. In chat you can tell the agent to use WRS_SEO_TOKEN and the /api/v1/snapshot endpoint.