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.
Zivtech is profiled on the APIs.io network. Tagged areas include Agency, Drupal, WordPress, Web Development, and Philadelphia.
Zivtech’s developer surface includes engineering blog and 5 more developer resources.
Kin Score
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 |
|---|---|---|---|---|
| Drupal Contributed-Module Ecosystem | 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.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
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
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.