Skip to content
ECZ-IDAPI
Free Passport: Get a FREE API Passport

At scale

Ownership across an API estate

Nobody has one API. They have a first-party estate, a set of partner-facing surfaces, a few inherited from an acquisition, and at least one nobody can name an owner for. One free Passport answers that question for one API. The estate view answers it for all of them at once.

The problem

Ownership decays faster than documentation

An API outlives the team that built it, the wiki page that described it and the person who knew why it exists. What is missing is rarely the endpoint; it is the name of whoever answers for it.

  • An estate is discovered, not designed

    Gateways, marketplaces, service catalogues and spreadsheets each hold part of the picture, and none of them agrees with the others about which entries are the same API.

  • A hostname is not an owner

    The thing a caller has is a base URL. Reaching an accountable organisation from it is, today, usually a matter of asking someone who might know.

  • Consolidation makes it worse

    After an acquisition the same logical API may appear under two organisations. One identity per logical API is how that resolves without renaming anything.

  • Agents will ask more often than people

    A machine caller has no colleague to ask. A public, machine-readable record is the only form of the answer it can use.

Optional

API Estate & Ownership

Ownership and identity across your whole API estate, rather than one API at a time.

The boundary

It records ownership. It is not a security test of any API and it never implies domain control.

Recording that your organisation owns an API is a declaration by your organisation. On its own it is not evidence that you control the domain the API answers on — only a binding completed through a live proof method shows that, as of its Last verified time — and it is not the result of any test against the API. The record is careful about that distinction so that a reader can be too.

Nothing here is required to hold a free API Passport, to publish its record or to have it resolved. An estate view is useful when you have an estate; one API needs one Passport and nothing else.

Tiers and price

What API Estate & Ownership costs, as TrustOps lists it

The tiers TrustOps publishes for this product, read from its projection. A price is not an offer to sell: each card states whether TrustOps can complete a purchase today.

  • API Estate & Ownership (monthly)

    Paid · Open

    £49.99 per month

    API Estate & Ownership: up to 50 API identities — an estate register for your API Passports; an accountable owner and a lifecycle stage (active, deprecated, sunset, retired) for each API; observation of each API's published OpenAPI document every 6 hours: content, version, operations, servers, security schemes, and whether it still carries its x-ecz-id backlink; every change recorded as a dated event in a local, hash-chained record you can export (JSON / CSV). Delivered in the Estate Operations console. Not included: that an API is secure or verified; runtime traffic monitoring; any change to the public Resolver; anchoring of the record.

    API identities
    50 API identities
    Choose API Estate & Ownership(opens in a new tab — trustops.ecocitizenz.com)

  • API Estate & Ownership (annual)

    Paid · Open

    £499 per year

    • One payment for 12 months (annual prepaid; it does not renew)

    API Estate & Ownership: up to 50 API identities — an estate register for your API Passports; an accountable owner and a lifecycle stage (active, deprecated, sunset, retired) for each API; observation of each API's published OpenAPI document every 6 hours: content, version, operations, servers, security schemes, and whether it still carries its x-ecz-id backlink; every change recorded as a dated event in a local, hash-chained record you can export (JSON / CSV). Delivered in the Estate Operations console. Not included: that an API is secure or verified; runtime traffic monitoring; any change to the public Resolver; anchoring of the record. One payment for exactly 12 months. It does not renew.

    API identities
    50 API identities
    Buy annual(opens in a new tab — trustops.ecocitizenz.com)

  • API Estate & Ownership Business (monthly)

    Paid · Open

    £149.99 per month

    API Estate & Ownership Business: up to 250 API identities — an estate register for your API Passports; an accountable owner and a lifecycle stage (active, deprecated, sunset, retired) for each API; observation of each API's published OpenAPI document every 6 hours: content, version, operations, servers, security schemes, and whether it still carries its x-ecz-id backlink; every change recorded as a dated event in a local, hash-chained record you can export (JSON / CSV). Delivered in the Estate Operations console. Not included: that an API is secure or verified; runtime traffic monitoring; any change to the public Resolver; anchoring of the record.

    API identities
    250 API identities
    Choose API Estate & Ownership Business(opens in a new tab — trustops.ecocitizenz.com)

  • API Estate & Ownership Business (annual)

    Paid · Open

    £1499 per year

    • One payment for 12 months (annual prepaid; it does not renew)

    API Estate & Ownership Business: up to 250 API identities — an estate register for your API Passports; an accountable owner and a lifecycle stage (active, deprecated, sunset, retired) for each API; observation of each API's published OpenAPI document every 6 hours: content, version, operations, servers, security schemes, and whether it still carries its x-ecz-id backlink; every change recorded as a dated event in a local, hash-chained record you can export (JSON / CSV). Delivered in the Estate Operations console. Not included: that an API is secure or verified; runtime traffic monitoring; any change to the public Resolver; anchoring of the record. One payment for exactly 12 months. It does not renew.

    API identities
    250 API identities
    Buy annual(opens in a new tab — trustops.ecocitizenz.com)

Read from the TrustOps projection generated . TrustOps owns purchase, payment and entitlement; the Dashboard operates the estate; the Resolver keeps proving exactly what it proved before. Buying never changes a record.

Preparing for an enterprise customer’s security review rather than mapping an estate? The API Enterprise Security Review & Customer Assurance Kit is built for that.

Read this before you assume

What an estate record is not

An ECZ-ID does not make anything safe, certified, approved or compliant, and holding one does not make you compliant with anything.
  • It is not an inventory scan. ECZ-ID discovers nothing about your network; it reads only the proof you publish for a binding.
  • It is not a security assessment. No API on a record has been tested, and a record never says otherwise.
  • It is not proof of domain control. A declared origin is a declaration, and a reader should treat it as one; only a binding completed through a live proof method shows control, and only as of its Last verified time.
  • It is not an authorisation decision. Whether a caller may reach an API is settled by your gateway and your tokens, not by a public record.

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

Where next

Keep going with ECZ-ID API.

Get a FREE API Passport