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
PNC website screenshot

PNC

PNC Financial Services Group is a Pittsburgh-based money-center bank and Fortune 500 diversified financial services company offering retail banking, corporate and institutional banking, treasury management, asset management, and residential mortgage banking across the United States. PNC operates a real first-party developer portal at developer.pnc.com ("PNC Developer Tools: Open APIs for Banking & Payments") that publishes a catalog of treasury and payments API products — including Account Verification Services, ePayments, Real-Time Payments (RTP), Direct-to-Debit-Card (push-to-card) disbursement, and information reporting — surfaced through its PINACLE commercial banking platform and PINACLE Connect embedded-banking integrations. Full API reference documentation, sandbox/testing environments, and call codes are gated behind credentialed onboarding arranged through a PNC Relationship Manager or Treasury Management Officer; no OpenAPI/Swagger specifications are publicly downloadable. On the consumer open-finance side, PNC exposes account data through an Akoya-provided tokenized data-access API and signed a bilateral data-access agreement with Plaid in September 2024, positioning PNC ahead of CFPB Section 1033 personal-financial-data-rights requirements.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles PNC the way a machine reads it — 8 machine-readable artifacts across 6 APIs, 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 — PNC scores 23.4/100 (emerging), with a separate agent-readiness read of 7/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 — 23.4/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 4.8 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Regulatory · Banking & Open Finance 6.5 / 15
Agent readiness — 7/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 4 / 4
Consent & Bot Identity 3 / 3

How we profile PNC

Each block below is one kind of artifact we hold for PNC. 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.

APIs 6

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

PNC Account Verification Services API

Account Verification Services API from PNC's developer portal for confirming the ownership and status of bank accounts before disbursing or collecting funds, helping corporate a...

PNC ePayments API

ePayments API from PNC's developer portal for programmatically initiating and tracking electronic payments — including ACH, wire transfers, and Real-Time Payments (RTP) — from c...

PNC Real-Time Payments (RTP) API

Real-Time Payments API surface from PNC, one of the first U.S. banks to adopt The Clearing House RTP network. PNC has built RTP-related APIs that let clients embed instant, 24/7...

PNC Direct-to-Debit-Card (Push-to-Card) API

Direct-to-Debit-Card (DTD) API from PNC providing an efficient option for business-to-consumer (B2C) fund disbursement by pushing payments directly to a recipient's debit card. ...

PNC Information Reporting API

Information reporting API surface from PNC for programmatic, near-real-time access to account balances, transaction history, and account detail across a client's PNC treasury ac...

PNC Consumer Data Access API (Akoya)

Consumer open-finance data-access surface through which PNC lets its retail customers securely permission and share account data with third-party financial apps without handing ...

Security Posture 2

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.

Pnc Domain Security

TLSv1.3 · DMARC

SECURITY

Pnc Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Every other property we hold for PNC — 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.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

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