pseo-engine
Programmatic SEO as callable tools.
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетНужен API-ключГлобальныйБесплатноМожет изменять данные
Что умеет
- Seo.Project.List: Lists every programmatic-SEO project this API key can act on, with id, name, slug, custom domain and page count. Call this FIRST in any session — every other tool needs a projectId f
- Seo.Project.Create: Creates a new programmatic-SEO project and returns its projectId. Call this when seo.project.list comes back empty — every other tool needs a projectId and a new account has none.
- Seo.Project.Get: Returns one project's settings and whether it is configured enough to generate content (needs both a field mapping and a content spec). Use this before seo.content.generate to avoid s
Какие данные видит
Нужен ли аккаунт
Нужен API-ключ из настроек сервиса
Programmatic SEO as callable tools. Research keywords, generate landing pages, audit them and publish — driven by your agent instead of a dashboard.
Keys are prepaid: listing tools is free, running them draws down a balance you buy once. Each key has its own daily spend cap and an itemized ledger.
Список инструментов сервера (9)
Технические названия из tools/list. Нужны только разработчикам.
| seo.project.list | Lists every programmatic-SEO project this API key can act on, with id, name, slug, custom domain and page count. Call this FIRST in any session — every other tool needs a projectId from here, and ids cannot be guessed or carried over from another account. FREE — this call costs nothing. |
| seo.project.create | Creates a new programmatic-SEO project and returns its projectId. Call this when seo.project.list comes back empty — every other tool needs a projectId and a new account has none. The project is created EMPTY: it still needs a data source and a content spec before seo.content.generate will run, so call seo.project.get afterwards and read readinessNote. FREE — this call costs nothing. |
| seo.project.get | Returns one project's settings and whether it is configured enough to generate content (needs both a field mapping and a content spec). Use this before seo.content.generate to avoid starting a run that will immediately fail. FREE — this call costs nothing. |
| seo.rows.list | Returns a page of rows (individual generated pages) with slug, target keyword and status. Statuses are PENDING (no content yet), GENERATING, GENERATED (draft), REVIEWED (approved), PUBLISHED (live), FAILED, FLAGGED_DUPLICATE. Content bodies are NOT included — this is a listing, not an export. Costs 3c per call. |
| seo.job.status | Returns the most recent background job for a project: type, status (QUEUED/RUNNING/COMPLETED/FAILED/CANCELLED), progress counters and the last log line. Poll this every few seconds after any tool that starts a job. Do NOT re-call the start tool while status is RUNNING; it will be refused. FREE — this call costs nothing. |
| seo.research.start | ASYNCHRONOUS. Starts a keyword-research run that mines and qualifies keywords into PENDING rows. It spends real AI budget, so call it once and then poll seo.job.status until status is COMPLETED. Returns immediately with a jobId — the keywords do NOT exist yet when this returns. Fails if a research run is already in progress. Costs 750c per call. |
| seo.content.generate | ASYNCHRONOUS. Starts the content-generation queue over every PENDING row in the project. It also spends real AI budget per generated page. Requires the project to be configured (check readyToGenerate via seo.project.get first). Returns a jobId immediately; poll seo.job.status. Generated pages land in GENERATED status and are NOT live until approved and published. Costs 75c per call. |
| seo.audit.start | ASYNCHRONOUS. Scans all generated pages for broken text, unfilled placeholders, truncated copy and missing images, recording findings per page. Returns a jobId; poll seo.job.status. This only REPORTS problems — it does not fix them. Costs 30c per call. |
| seo.publish | SYNCHRONOUS. Takes approved pages live. IMPORTANT: only rows in REVIEWED status are published — GENERATED drafts are deliberately skipped, because approval is a human gate in this product. The response reports how many were skipped and why; if publishedCount is 0 and skippedNeedsReview is high, the pages need approving in the dashboard first. Costs 15c per call. |