> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pcnaid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Partner Documentation

> The implemented DealerOS provider-integration path and unverified commercial program details.

# Partner Documentation

DealerOS has an implemented technical engagement path for service providers. A provider implementation declares its category, operations, capabilities, credential-reference requirements, data classifications, and idempotency or reconciliation behavior. DealerOS then exposes tenant-specific enablement and fallback order through its Providers workspace.

## Implemented engagement model

| Stage | What DealerOS implements |
| - | - |
| Adapter registration | A provider is registered against an existing operation and capability contract. |
| Tenant enablement | A dealership administrator connects or disconnects an available provider entitlement. |
| Routing | A dealership sets provider order by category so the runtime can try entitled providers in sequence. |
| Credentials | Tenant configuration stores references to managed secrets or connections, not credential values. |
| Operations | The runtime validates capability, rights, credential reference, and idempotency requirements before dispatch. |
| Reporting | Provider health, last error, and recent usage are shown in the Providers workspace. |
| Webhooks | Supported inbound provider events are signature-verified and stored with deduplication. |

Technical teams can use the [architecture overview](https://docs.pcnaid.com/nodes/web-apps/dealeros/developer/architecture-overview.md) and [API reference](https://docs.pcnaid.com/nodes/web-apps/dealeros/developer/api/index.md) to evaluate the implemented boundary.

## Not yet documented — implementation not verified

The reviewed source does not define a public partner enrollment flow, certification process, affiliate or referral program, commissions, revenue examples, reseller terms, co-marketing terms, partner support SLA, or downloadable partner agreements. Those topics are deliberately not described here until an implementation or owner-approved source exists.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.