Naftiko-branded framing was purged from the apis.io network on 2026-06-23 — NaftikoCapability artifacts stripped at load, capabilities pages deleted, the property removed from scoring, links purged from llms.txt/READMEs/apis.yml across the catalog.
That purge was scoped to api-search/*. It never reached api-commons. Eight files in the hub still carry it.
The property page
_community/naftiko-capability.md — a live building block on apicommons.org: "NaftikoCapability", tagged Naftiko, describing "the deployable unit of the Naftiko platform."
Every other entry in _common and _community describes a format or an operational fact — an OpenAPI, a changelog, a rate limit, a plan. Vendor-neutral by construction; that is the premise of a commons. NaftikoCapability describes one company's proprietary deployment unit, sitting alongside openapi and json-schema.
Five common properties cite it as a governance-rule source
| File |
Reference |
_common/lifecycle.md |
id: naftiko-lifecycle, source: Naftiko Sandbox (lifecycle/*.yml) |
_common/rate-limits.md |
id: naftiko-rate-limits |
_common/status-page.md |
id: naftiko-status-page |
_common/error-codes.md |
id: naftiko-error-codes |
_common/pricing.md |
naftiko-plans, plus a tool entry linking github.com/naftiko |
These render publicly as governance rules, listed next to Spectral built-in — so a single vendor's sandbox reads as a peer of the linter's own rules. Either the rules exist and can be pointed at, or the citation should go.
Two blog posts
_posts/2026-05-20-the-integrations-page-as-an-api-commons-artifact.md and _posts/2026-04-21-spec-driven-integration-capability-specs-as-shared-integration-artifacts.md. These are published editorial — dated, written, part of the record. Rewriting history is worse than leaving it; they are listed for completeness, not for removal.
Recommended
- Delete
_community/naftiko-capability.md.
- Drop or rename the five
naftiko-* governance-rule citations. If the underlying rules are real and reachable, cite them by what they are; if not, remove them.
- Leave the blog posts.
What is not being said
Naftiko as a company is a normal catalog entry, scored and swept like any other provider. This is about branded framing in API Commons' own surfaces.
Naftiko-branded framing was purged from the apis.io network on 2026-06-23 —
NaftikoCapabilityartifacts stripped at load, capabilities pages deleted, the property removed from scoring, links purged fromllms.txt/READMEs/apis.ymlacross the catalog.That purge was scoped to
api-search/*. It never reached api-commons. Eight files in the hub still carry it.The property page
_community/naftiko-capability.md— a live building block on apicommons.org: "NaftikoCapability", taggedNaftiko, describing "the deployable unit of the Naftiko platform."Every other entry in
_commonand_communitydescribes a format or an operational fact — an OpenAPI, a changelog, a rate limit, a plan. Vendor-neutral by construction; that is the premise of a commons.NaftikoCapabilitydescribes one company's proprietary deployment unit, sitting alongsideopenapiandjson-schema.Five common properties cite it as a governance-rule source
_common/lifecycle.mdid: naftiko-lifecycle,source: Naftiko Sandbox (lifecycle/*.yml)_common/rate-limits.mdid: naftiko-rate-limits_common/status-page.mdid: naftiko-status-page_common/error-codes.mdid: naftiko-error-codes_common/pricing.mdnaftiko-plans, plus a tool entry linkinggithub.com/naftikoThese render publicly as governance rules, listed next to
Spectral built-in— so a single vendor's sandbox reads as a peer of the linter's own rules. Either the rules exist and can be pointed at, or the citation should go.Two blog posts
_posts/2026-05-20-the-integrations-page-as-an-api-commons-artifact.mdand_posts/2026-04-21-spec-driven-integration-capability-specs-as-shared-integration-artifacts.md. These are published editorial — dated, written, part of the record. Rewriting history is worse than leaving it; they are listed for completeness, not for removal.Recommended
_community/naftiko-capability.md.naftiko-*governance-rule citations. If the underlying rules are real and reachable, cite them by what they are; if not, remove them.What is not being said
Naftiko as a company is a normal catalog entry, scored and swept like any other provider. This is about branded framing in API Commons' own surfaces.