// B2B PREDICTIVE ANALYTICS API
What a B2B predictive analytics API is — and how ForeMetric delivers one without personal data
A B2B predictive analytics API is an endpoint that returns forecasts about audience behaviour — churn probability, lifetime value, next best action, cohort intent — instead of raw event logs. Your team sends a question; the API answers with a score, a confidence level and the factors behind it. ForeMetric provides that layer on top of consented behavioural signals from real, verified people, processed inside hardware enclaves so no personally identifiable information ever reaches the buyer.
How the ForeMetric predictive API works
Signals are captured on the user's own device, stripped of identifiers locally, and encrypted before they leave the phone. Computation happens inside isolated Trusted Execution Environments (ARM TrustZone and Apple Secure Enclave on-device; disclosed trusted-operator key custody in Phase 1 and AMD SEV-SNP + COCOON TDX (Phase 2, Q1 2027) attested enclaves in Phase 2 on the server side). A query never touches raw logs — it touches vectors that only exist inside the enclave.
The response you receive is deliberately narrow: an aggregated cohort prediction plus a cryptographic attestation proving the computation ran inside a genuine enclave on genuine, Proof-of-Behavior-verified signals. Buyers cannot reconstruct an individual from an answer, which is exactly what makes the data legally durable.
- Cohort predictions: churn probability, LTV estimation, next best action.
- Audience Radar profiles: aggregated behavioural patterns with no PII.
- Attestation: proof the computation ran inside a secure TEE (Phase 2, Q1 2027) on verified signals.
- Settlement: every query is metered and paid on the TON blockchain.
Why this is different from cookies, panels and data brokers
Third-party cookie pools and broker databases degrade fast: consent is questionable, identity graphs drift, and a growing share of the traffic behind them is synthetic. Survey panels are cleaner but tiny and self-reported. ForeMetric sits in a third category — continuous, cross-context behavioural signal, contributed knowingly by the person it describes.
Every signal is filtered through Proof-of-Behavior, a consensus layer combining cryptographic validity, interaction micro-timing biometrics and cross-stream verification, with a target bot-filtering accuracy of 93–97%. You are not paying for bot traffic, and you are not inheriting somebody else's consent problem.
Consent, compliance and the Signal Passport
Access is governed by the Signal Passport: the person decides which signal sectors are visible, how many times they can be queried, and for how long — and can revoke that permission on-chain at any moment. Revocation removes the technical ability to decrypt those signals for new queries, which is what makes the right to be forgotten enforceable rather than procedural.
This is Privacy by Design in the GDPR Article 25 sense, applied at protocol level rather than bolted on as policy. Up to 80% of net B2B revenue flows back to the people whose signals produced the answer, which is also why consent here is durable: contributors are paid participants, not tracked subjects.
Where teams use it
The API is built for questions that traditional analytics answers late or not at all — the ones where behaviour outside your own product is the missing variable.
- Retention teams: flag accounts crossing a churn-risk threshold before the cancellation, not after it.
- Growth and AdTech: target verified behavioural cohorts instead of decaying cookie segments.
- AI labs: source verified, consented human signal for training and evaluation.
- Fintech, DeFi and Insurtech: enrich risk models with cross-context activity patterns.
Want to see the exact query format, cohort output and attestation payload? The whitepaper documents the API surface, the tokenomics behind query settlement, and the enclave architecture in full.
Read the whitepaper →