Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Zivtech website screenshot

Zivtech

Zivtech is a Philadelphia-based digital design and development agency founded in 2008, specializing in open-source web platforms (Drupal and WordPress) for mission-driven organizations including universities, hospitals, museums, and foundations. Founder and CEO Alex Urevick-Ackelsberg leads a small team (~10 staff) serving clients such as Children's Hospital of Philadelphia, Rutgers University, Temple University, Johns Hopkins Bloomberg School of Public Health, the Institute for Advanced Study, the Science History Institute, and the John Templeton Foundation. Their tagline: "We design and build technology that helps progressive organizations meet ambitious goals." Zivtech is a services firm — not an API provider. They build custom Drupal and WordPress sites, mobile applications, and digital experiences for clients, but they do not publish or operate any public APIs, SDKs, developer portals, pricing, status pages, or OpenAPI artifacts of their own. Their value lies in professional services and long-term client partnerships rather than a product or platform with a programmable surface area. For API Evangelist purposes this repo serves only as a registry placeholder confirming the agency's existence, scope, and status.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Zivtech the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zivtech scores 7.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 7.2/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Zivtech

Each block below is one kind of artifact we hold for Zivtech. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Zivtech Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Zivtech — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/zivtech · machine-readable index on apis.io