Ferro Corporation

Ferro Corporation was a Cleveland-area, NYSE-listed (FOE) Fortune 1000 producer of functional coatings, color solutions, glass enamels, pigments and electronic materials. In April 2022 it was acquired by Prince International (American Securities) and merged with Prince and Chromaflo to form Vibrantz Technologies (vibrantz.com); Ferro filed a Form 15 with the SEC on 2022-05-02 and ferro.com now 301-redirects to vibrantz.com. Neither the legacy Ferro brand nor Vibrantz publishes a developer program, an API reference or a machine-readable contract: api.ferro.com and developer.ferro.com do not resolve, vibrantz.com answers 404 on every developer, OpenAPI and /.well-known/ path probed on 2026-09-17, and its only machine-readable surfaces are a Yoast-generated llms.txt, an RSS feed and the default WordPress /wp-json/ index. Machine-readable company data exists only through third-party channels — Ferro's historical SEC filings (CIK 0000035214) remain on the SEC's own EDGAR APIs.

Ferro Corporation is listed with 1 API on the APIs.io network. Tagged areas include Functional Materials, Electronics, Chemicals, Specialty Chemicals, and Pigments.

Ferro Corporation’s developer surface includes engineering blog and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

18.5/100 emerging ▬ flat Agent 1/100 human only Front door AI 1/6 silent Heartbeat 93/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

1 API

Functional MaterialsElectronics Chemicals Specialty Chemicals Pigments CoatingsVibrantz TechnologiesAcquired Fortune 1000

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 18.5/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 5.8 / 17

Operational Transparency 0.6 / 11

Contract Governance 0.0 / 10

Discoverability 6.3 / 9

Regulatory Posture 2.1 / 15

Agent readiness — 1/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/ferro/"><img src="https://apis.io/badge/ferro/card.svg" alt="Ferro Corporation on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 19.0 — up to +16.2 composite points
Access Clarity scores 34.2 — up to +13.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/ferro/apis.yml: open an issue on github.com/api-evangelist/ferro to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Chemistry and Materials (chemical data depositors, materials-data APIs)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

SEC EDGAR Filings (Ferro Corporation, CIK 0000035214)

Machine-readable historical filing data for Ferro Corporation is available from the U.S. Securities and Exchange Commission, not from the company. The SEC EDGAR submissions API ...

Ferro Corporation API pricing

Not yet checked against Ferro Corporation's own pricing page. Compiled by API Evangelist on 2026-05-05 from vibrantz.com/; confirm before you rely on a figure.

Plan	Price
No Public API enterprise	—

Plan details, limits and sources →

Rate limits

No public API surface: not applicable; no public API exists varies

Compiled by API Evangelist, not yet checked against Ferro Corporation's documentation. Rate-limit details →

Billed by: not applicable · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Ferro Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Ferro Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Ferro Finops

FINOPS

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Ferro Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

Contact

Contact

PressReleases

PressReleases

Commercial 4

Pricing, plans, and the legal terms of use

Plans

FinOps

PrivacyPolicy

TermsOfService

Company 7

The organization behind the API

Website

Website

Careers

Blog

BlogRSS

LinkedIn

Scroll for all 7

Source (apis.yml)

aid: ferro
url: https://raw.githubusercontent.com/api-evangelist/ferro/refs/heads/main/apis.yml
name: Ferro Corporation
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  gated_conflict: 'x-api-posture: private but 1 published API entry'
  label: Enterprise
  confidence: low
  probe_state: none
  source:
  - plans
  - security
  - url: https://www.ferro.com
    status: 301
    note: declared website redirects to https://vibrantz.com/ — a different registrable domain (ferro.com -> vibrantz.com),
      possible rename or acquisition (probed 2026-09-03, roadmap#169)
  - url: https://vibrantz.com/developers/
    status: 404
    note: successor site publishes no developer program; api.ferro.com and developer.ferro.com are NXDOMAIN (probed 2026-09-17)
  generated: '2026-11-06'
  method: derived
position: Consuming
access: 3rd-Party
x-api-posture: no-product-api
x-api-posture-basis: observed
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/ferro.png
tags:
- Functional Materials
- Electronics
- Chemicals
- Specialty Chemicals
- Pigments
- Coatings
- Vibrantz Technologies
- Acquired
- Fortune 1000
tags_raw:
- Functional Materials
- Electronics
- Chemical
- Specialty Chemicals
- Pigments
- Coatings
- Vibrantz Technologies
- Acquired
- Fortune 1000
description: 'Ferro Corporation was a Cleveland-area, NYSE-listed (FOE) Fortune 1000 producer of functional coatings, color
  solutions, glass enamels, pigments and electronic materials. In April 2022 it was acquired by Prince International (American
  Securities) and merged with Prince and Chromaflo to form Vibrantz Technologies (vibrantz.com); Ferro filed a Form 15 with
  the SEC on 2022-05-02 and ferro.com now 301-redirects to vibrantz.com. Neither the legacy Ferro brand nor Vibrantz publishes
  a developer program, an API reference or a machine-readable contract: api.ferro.com and developer.ferro.com do not resolve,
  vibrantz.com answers 404 on every developer, OpenAPI and /.well-known/ path probed on 2026-09-17, and its only machine-readable
  surfaces are a Yoast-generated llms.txt, an RSS feed and the default WordPress /wp-json/ index. Machine-readable company
  data exists only through third-party channels — Ferro''s historical SEC filings (CIK 0000035214) remain on the SEC''s own
  EDGAR APIs.'
created: '2026-04-19'
modified: '2026-09-17'
specificationVersion: '0.23'
apis:
- aid: ferro:sec-edgar-filings
  name: SEC EDGAR Filings (Ferro Corporation, CIK 0000035214)
  description: Machine-readable historical filing data for Ferro Corporation is available from the U.S. Securities and Exchange
    Commission, not from the company. The SEC EDGAR submissions API returns the full filing history for CIK 0000035214 (FERRO
    CORP) as JSON — 10-K, 10-Q, 8-K and proxy filings through the 2022 acquisition, the Form 15-12B deregistration of 2022-05-02,
    and beneficial-ownership amendments into 2023. This is a third-party government API listed here because it is the only
    real programmatic access to this company's data; Ferro no longer files.
  humanURL: https://www.sec.gov/search-filings/edgar-application-programming-interfaces
  baseURL: https://data.sec.gov
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  tags:
  - Filings
  - SEC EDGAR
  - Third Party
  tags_raw:
  - Filings
  - SEC EDGAR
  - Third-Party
  properties:
  - type: Documentation
    url: https://www.sec.gov/search-filings/edgar-application-programming-interfaces
  - type: APIReference
    url: https://data.sec.gov/submissions/CIK0000035214.json
  x-evidence:
    verified: '2026-09-17'
    method: fetched documentation and called the endpoint
    documentation: The SEC's EDGAR APIs page (HTTP 200) documents RESTful JSON APIs on data.sec.gov — https://data.sec.gov/submissions/CIK##########.json
      plus the XBRL companyconcept, companyfacts and frames APIs. No authentication or API key is required; a declared User-Agent
      and a 10-request-per-second ceiling are the stated fair-access terms.
    endpoint_check: GET https://data.sec.gov/submissions/CIK0000035214.json returned HTTP 200 with JSON naming "FERRO CORP",
      no current ticker, and 1,000 recent filings whose latest entries are an SC 13G/A dated 2023-02-10 and the 15-12B dated
      2022-05-02.
common:
- type: Plans
  url: plans/ferro-plans-pricing.yml
- type: RateLimits
  url: rate-limits/ferro-rate-limits.yml
- type: FinOps
  url: finops/ferro-finops.yml
- type: Website
  url: https://vibrantz.com/
- type: Website
  url: https://www.ferro.com
- type: Contact
  url: https://vibrantz.com/contact-us/
- type: Careers
  url: https://vibrantz.com/careers/
- type: PressReleases
  url: https://vibrantz.com/press/
- type: Blog
  url: https://vibrantz.com/vibrantz-edge/
- type: BlogRSS
  url: https://vibrantz.com/feed/
- type: PrivacyPolicy
  url: https://vibrantz.com/privacy/
- type: TermsOfService
  url: https://vibrantz.com/legal/
- type: LinkedIn
  url: https://www.linkedin.com/company/ferro-corporation
- type: LinkedIn
  url: https://www.linkedin.com/company/vibrantztechnologies
- type: LLMsTxt
  url: llms/ferro-llms.txt
- type: DomainSecurity
  url: security/ferro-domain-security.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-09-17'
  status: minimal
  artifacts_added: 2
  pass: local-v3
x-coverage:
  state: none
  reason: defunct
  detail: Ferro Corporation was absorbed into Vibrantz Technologies in 2022 — ferro.com 301-redirects every path to the vibrantz.com
    root, the scaffolded hosts api.ferro.com and developer.ferro.com do not resolve in DNS, and vibrantz.com answers 404 on
    /developers/, /api/, /openapi.json and every /.well-known/ path, publishing only a Yoast llms.txt, an RSS feed and the
    default WordPress /wp-json/ index.
  evidence:
  - url: https://www.ferro.com/
    status: 301
  - url: https://vibrantz.com/developers/
    status: 404
  - url: https://vibrantz.com/openapi.json
    status: 404
  - url: https://vibrantz.com/.well-known/agent-card.json
    status: 404
  - url: https://vibrantz.com/llms.txt
    status: 200
  checked: '2026-09-17'

Ferro Corporation API — frequently asked questions

Does Ferro Corporation have an API?

Yes. APIs.io lists 1 API from Ferro Corporation, including SEC EDGAR Filings (Ferro Corporation, CIK 0000035214).

How much does the Ferro Corporation API cost?

APIs.io lists 1 pricing plan for Ferro Corporation, with each plan's price, limits and inclusions under Pricing on this page.

Is the Ferro Corporation API ready for AI agents?

Ferro Corporation has a Kin Score of 18.5 out of 100 (emerging) and an Agent Readiness score of 0.6 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/ferro"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/ferro/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/ferro/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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