Integration status · Planned
PAP integration,
validated against real business tasks.
Make support explicit: what was validated, with which client, and what remains. The first goal is one verifiable business task.
Current status: planned integration and validation
As of 2026-10-16, Frontvia has not publicly claimed interoperability acceptance for any PAP client and complete business workflow. This page lists validation targets, not live capabilities.
Publish the scope of each validation
| Validation | Acceptance | Status |
|---|---|---|
| Company discovery and entrance description | The target client correctly identifies the business, supported interactions and official information. | Planned validation |
| User sessions and authorization | Public and private access are separated; approval, revocation and failure paths are verified. | Planned validation |
| One business task | Query, approval, business execution and a clear receipt work with a specified client version. | Planned validation |
| Platform admission and discovery | Separately verify platform requirements, the real entrance and discovery path. | Planned validation |
| Real demand and business value | Record demand sources, actual outcomes and maintenance cost, not demo counts. | Planned validation |
What a PAP-compatible business agent should specify
- Protocol version and client name/version.
- Validated business actions, access rights and confirmation boundaries.
- Test date, reproducible outcomes and remaining gaps.
- Technical compatibility, platform approval and demand outcomes stated separately.
Start with the business you already run.
Tell us what you offer and one task you want a customer’s agent to complete. The product is in development; pilot scope will be agreed around real needs.