Cresilon

Cresilon SEO Metadata API

Public Yoast SEO head endpoint returning the rendered SEO/head metadata and its schema.org JSON-LD graph for any cresilon.com URL — the cheapest structured description of a Cresilon page for an agent.

Documentation GitHub OpenAPI

Operations 1

GET /yoast/v1/get_head Get rendered SEO head metadata for a Cresilon URL #

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/cresilon-seo-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 email required.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Cresilon Metadata SEO API
  version: wp/v2
  summary: Yoast SEO head and JSON-LD graph for any cresilon.com URL.
  description: Cresilon publishes its corporate website (cresilon.com) on WordPress (WordPress.com Atomic hosting, nginx) with the core WordPress REST API enabled and anonymously readable. This specification was DERIVED by discovering the live route index at https://cresilon.com/wp-json/ and probing each route for anonymous access; only routes verified to return HTTP 200 without credentials are documented here as public operations. Write operations exist on the same routes but require authentication (WordPress cookie + X-WP-Nonce, or Application Passwords) and are not documented here; anonymous requests to them return HTTP 401. This is NOT a product API offered by Cresilon to customers — Cresilon is a biotechnology and medical-device manufacturer, not a software vendor. This is the content API of their marketing site, captured for discovery purposes. This document covers the Yoast SEO `get_head` route, which returns the rendered SEO metadata and the JSON-LD schema graph for any cresilon.com URL. For an agent this is the cheapest structured description of a Cresilon page — organization identity, canonical URL, social cards and article metadata — without parsing the page HTML.
  contact:
    name: Cresilon
    url: https://cresilon.com/contact-us/
    email: info@cresilon.com
  license:
    name: Site content — all rights reserved, see Terms of Use
    url: https://cresilon.com/terms-of-use/
  x-apis-io-provenance:
    method: derived
    source: https://cresilon.com/wp-json/
    derived_on: '2026-08-04'
    note: Routes enumerated from the live wp-json discovery document (1,021 routes across 45 namespaces); every operation below was probed anonymously and returned HTTP 200. Schemas reflect the field set observed in live responses on 2026-08-04, including the `acf` (Advanced Custom Fields), Jetpack and `yoast_head_json` extensions this site adds. No fabricated operations or parameters.
servers:
- url: https://cresilon.com/wp-json
  description: Production
tags:
- name: SEO
  description: Rendered SEO head metadata and JSON-LD structured data.
paths:
  /yoast/v1/get_head:
    get:
      tags:
      - SEO
      operationId: getYoastHead
      summary: Get rendered SEO head metadata for a Cresilon URL
      description: Yoast SEO head endpoint. Returns the rendered `<head>` SEO markup for any cresilon.com URL together with its structured JSON-LD `schema` graph (Organization, WebSite, WebPage, BreadcrumbList and Article nodes). Verified live 2026-08-04 against the home page and /our-story/.
      parameters:
      - name: url
        in: query
        required: true
        description: The cresilon.com URL to render SEO metadata for.
        schema:
          type: string
          format: uri
      responses:
        '200':
          description: Rendered SEO head and its JSON-LD graph.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/YoastHead'
              examples:
                ourStory:
                  summary: SEO head for /our-story/
                  externalValue: https://cresilon.com/wp-json/yoast/v1/get_head?url=https%3A%2F%2Fcresilon.com%2Four-story%2F
        '404':
          $ref: '#/components/responses/NotFound'
components:
  schemas:
    Error:
      type: object
      description: The WordPress REST error envelope, verified live against cresilon.com. Note this is NOT RFC 9457 application/problem+json — it is served as application/json with a WordPress-specific shape.
      properties:
        code:
          type: string
          description: Machine-readable WordPress error code, e.g. `rest_post_invalid_id`.
        message:
          type: string
          description: Human-readable message.
        data:
          type: object
          properties:
            status:
              type: integer
              description: HTTP status code, repeated in the body.
            params:
              type: object
              additionalProperties:
                type: string
            details:
              type: object
              additionalProperties: true
          required:
          - status
      required:
      - code
      - message
      - data
    YoastHead:
      type: object
      description: Yoast SEO head payload for a URL. Field set observed live on 2026-08-04.
      properties:
        json:
          type: object
          additionalProperties: true
          description: 'Structured SEO metadata: title, description, canonical, og_*, twitter_*, and the JSON-LD `schema` graph.'
        html:
          type: string
          description: The rendered `<head>` SEO markup as an HTML string.
  responses:
    NotFound:
      description: The requested object does not exist.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            code: rest_post_invalid_id
            message: Invalid post ID.
            data:
              status: 404