PageAudit Tools API

The Tools API from PageAudit — 4 operation(s) for tools.

Operations 4

GET /api/tools The micro-tools: one landing per check, all driven by the same engine as the… #
GET /api/tools/{slug} Metadata and copy of one micro-tool #
GET /tools HTML hub of the micro-tools, indexable. For JSON use `GET /api/tools` #
GET /tools/{slug} HTML landing of one check, indexable. An unknown slug returns a real 404 #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/pageaudit-tools-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

pageaudit-tools-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: PageAudit Tools API
  version: f5ac3ca0
  description: 'Technical SEO auditor that ships the fix. Main client: AI agents. Browsable index at GET /api/.'
servers:
- url: https://pageaudit.online
tags:
- name: Tools
paths:
  /api/tools:
    get:
      operationId: list_tools
      summary: 'The micro-tools: one landing per check, all driven by the same engine as the…'
      description: 'Returns: { tools[{slug,title,h1,description,lead,category,icon,checks,serp,sections,_links}], _links }'
      security: []
      responses:
        '200':
          description: '{ tools[{slug,title,h1,description,lead,category,icon,checks,serp,sections,_links}], _links }'
          content:
            application/json:
              schema:
                type: object
                properties:
                  tools:
                    type: array
                    items:
                      $ref: '#/components/schemas/Ferramenta'
                    description: Every published tool.
                  _links:
                    type: object
                    description: The hub in HTML and the API index.
                required:
                - tools
                - _links
      tags:
      - Tools
  /api/tools/{slug}:
    get:
      operationId: get_tool
      summary: Metadata and copy of one micro-tool
      description: 'Returns: { slug, title, h1, description, lead, category, icon, checks, serp, sections, _links }'
      security: []
      parameters:
      - name: slug
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: '{ slug, title, h1, description, lead, category, icon, checks, serp, sections, _links }'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Ferramenta'
        '404':
          description: Unknown slug.
      tags:
      - Tools
  /tools:
    get:
      operationId: get_tools
      summary: HTML hub of the micro-tools, indexable. For JSON use `GET /api/tools`
      description: 'Returns: `text/html` — the hub page, rendered on the server.'
      security: []
      responses:
        '200':
          description: '`text/html` — the hub page, rendered on the server.'
      tags:
      - Tools
  /tools/{slug}:
    get:
      operationId: get_tools_by_slug
      summary: HTML landing of one check, indexable. An unknown slug returns a real 404
      description: 'The 404 is real, not a 200 with an empty shell: mass soft-404s burn the whole domain in the index.

        Returns: `text/html` — the tool''s landing.'
      security: []
      parameters:
      - name: slug
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: '`text/html` — the tool''s landing.'
        '404':
          description: Unknown slug — a real 404, not an empty shell.
      tags:
      - Tools
components:
  schemas:
    Ferramenta:
      type: object
      properties:
        slug:
          type: string
          description: Identifier in the URL, e.g. `title-tag-checker`.
        title:
          type: string
          description: Page title, used in `<title>`.
        h1:
          type: string
          description: The landing's H1.
        description:
          type: string
          description: Meta description of the landing.
        lead:
          type: string
          description: Opening paragraph.
        category:
          type: string
          description: Grouping of the tool in the hub.
        icon:
          type: string
          description: Name of the icon used in the card.
        checks:
          type: array
          items:
            type: string
          description: Finding codes this tool highlights — they are the `Achado.code`s.
        serp:
          type: object
          description: How the result looks in the search preview.
        sections:
          type: array
          items:
            type: object
          description: Content blocks of the landing.
        _links:
          type: object
          description: This tool in JSON and in HTML.
      required:
      - slug
      - title
      - h1
      - description
      - lead
      - category
      - icon
      - checks
      - serp
      - sections
      - _links
      description: 'A micro-tool: the landing of one isolated check, with the same engine as the full audit.'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'Guest token (`POST /api/guest`) in `X-Guest-Token: pa_…`, `Authorization: Bearer pa_…` or `?guest_token=pa_…`. A user session (`sess_…`) also works and takes precedence.'