Bring Your Own Provider: integration and authorization
Bring Your Own Provider means the customer retains its provider relationship and authorizes a defined integration scope. GridZen uses an approved adapter and route to normalize evidence. The current alpha does not accept arbitrary provider keys in a browser or request body.
Prepare the route
Record the provider product, country, event, permitted identifiers, account owner, credential handling and downstream evidence scope. Confirm whether server-side processing on behalf of the customer is allowed. A public API or an available account is not evidence of permission to sell the resulting data.
Test one bounded event
Start with one event and permitted non-production inputs. Check successful evidence, missing required inputs, upstream errors and unknown provider IDs. Inspect the trace for accidental raw identifiers. Twilio Lookup line-type evidence is not subscriber-name matching; each new product needs its own adapter and scope check.
Move beyond evaluation
Approve retention, deletion, access logging, policy ownership and operational recovery before live use. The controlled-pilot implementation has account authorization, route allowlists, encrypted audit and rate limiting; that bounded deployment does not establish general production readiness. Managed Provider Packs require an additional written commercial-rights review.
Sources and scope
Based on the alpha contract and source implementation. Live route availability requires separate confirmation.