Developer Agreement
Rules for API keys, scoped access, audit obligations, consent-gated reliability data, and prohibited developer uses.
405 Magnolia Road, Pemberton NJ, 08889
Keys and scope
Every API key is issued to a named application with declared scopes. You must keep keys confidential, rotate them where appropriate, and immediately revoke any key you believe may be compromised.
Keys are limited to the scopes granted. Access to protected reliability or identity-related data requires explicit consent and a corresponding audit trail.
Restricted developer uses
Developers may not attempt open legal-name search, broad profile scraping, shadow scoring, hidden surveillance, discriminatory profiling, resale of protected data, or any use that conflicts with PayToCommit’s consent model or applicable law.
Developers may not work around rate limits, retention rules, access revocations, or technical safeguards.
Audit and compliance
PayToCommit may suspend, limit, review, or terminate keys or applications that create risk, misuse protected data, exceed scope, or fail to meet audit and security expectations.
Developers must cooperate with incident response, misuse investigations, and data-subject handling where their application or use of PayToCommit data is implicated.