Provely verifies Resend, Shopify Admin API and Stripe today. Each service page is generated from the signed skill package, so it never claims a completion level the skill does not certify.
| Service | Completion levels | Certification | Skill version | Last conformance run |
|---|---|---|---|---|
| Resend | accepted, bounced, delivered, sent | Community | 0.1.0 | 2026-09-05T12:00:00Z |
| Shopify Admin API | created, financially_completed | Community | 0.1.0 | 2026-09-05T12:00:00Z |
| Stripe | created, succeeded | Community | 0.1.0 | 2026-09-05T12:00:00Z |
How is a service page made?
- The Integration Compiler reads the provider schema, docs, event samples, and sandbox experiments.
- It classifies side effects, infers lifecycles, discovers evidence channels, and synthesizes contracts and tests.
- The conformance harness runs the false-completion benchmark against the skill.
- The compiler certifies and signs the manifest.
- This site renders the page from that manifest. A skill change updates the page.
How do I get a service that is not listed?
Run provely skill generate --openapi <url> to draft a skill from a schema, review the uncertainties, and run the conformance matrix. A service becomes a compilation and conformance problem, not an integration project.