CallerAPI
★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey14 EndpointsREST
For Agents
Score a phone number for spam, retrieve carrier and HLR data, run KYC checks, and subscribe to daily spam reports through CallerAPI.
Use for: I need to get the spam score for a phone number, Retrieve HLR carrier data for an international number, Run a KYC identity check on a phone number, Find out when a phone number was last ported
Not supported: Does not handle outbound call placement, SMS sending, or call recording — use for phone number intelligence, KYC, and spam reporting only.
Jentic publishes the only available OpenAPI specification for CallerAPI, keeping it validated and agent-ready. CallerAPI delivers phone number intelligence — spam score, HLR (Home Location Register) carrier data, KYC and identity verification, ported date and porting history, and online presence signals derived from messaging and social platforms. It also exposes a webhook subscription system for daily spam reports, plus upload endpoints for submitting your own spam reports and contacts to enrich the shared dataset. Authentication is an x-api-key header on every request, and the 14 operations are grouped under Lookup, Reports, Upload, and Account.
Install Jentic One Beta
Connect the CallerAPI to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CallerAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with CallerAPI API.
Score a phone number for spam likelihood and retrieve HLR carrier data via /api/v1/spam-score
Run KYC and identity verification checks on a phone number via /api/v1/kyc
Look up a number's last ported date and full porting history
Check online presence across messaging and social platforms with /api/v1/online-presence
Subscribe and unsubscribe webhooks to receive daily spam reports
Upload spam reports or contact lists to enrich the CallerAPI dataset
Track remaining credits on the account through /api/v1/account/balance
Use Cases
Patterns agents use CallerAPI API for, with concrete tasks.
★ Spam Score and Carrier Validation
Before initiating outbound calls or SMS, query /api/v1/spam-score to get both a spam likelihood and the underlying HLR carrier record for the destination number. This tells the agent whether the number is live, which carrier hosts it, and whether it has been reported as spam — a single call replaces separate lookups against carrier and reputation services.
GET /api/v1/spam-score with the phone number and route the call only when the spam score is below the configured threshold.
Phone-Based KYC and Identity Verification
For lightweight identity verification flows, call /api/v1/kyc with the phone number to retrieve associated identity signals such as ported date, porting history, and online presence. This is much cheaper than document-based KYC and is well-suited to first-line fraud screening before escalating high-risk users to a full document verification provider.
GET /api/v1/kyc with the phone number and pass through to a document KYC provider only when the identity score falls below threshold.
Daily Spam Report Webhook
Subscribe to daily spam reports by POSTing to /api/v1/webhooks/subscribe and receive batches of newly reported numbers at the configured URL. Use /api/v1/webhooks/test to verify reachability and /api/v1/webhooks/dispatch to manually trigger a redelivery during incident response. The reports feed your block lists without polling.
POST a webhook subscription to /api/v1/webhooks/subscribe with the receiver URL, then call /api/v1/webhooks/test to confirm the endpoint is reachable.
Bulk Contact Enrichment
Upload a batch of contacts to /api/v1/upload/contacts to enrich them in one request rather than calling spam-score for each number. The same Upload tag also exposes /api/v1/upload/spam-reports for sending your own user-reported spam back into the shared dataset, which both improves the global signal and ensures your reports are reflected in future scores.
POST a CSV of contacts to /api/v1/upload/contacts and write the returned enriched rows back to the contact database.
AI Agent Phone Intelligence via Jentic
Through Jentic, an AI agent searches for an intent like 'check the spam score of a phone number' and is returned the CallerAPI spam-score operation along with its input schema. The agent calls the operation without ever holding the raw x-api-key value, and can chain into KYC, ported-date, or online-presence checks based on the spam score response. Setup time is under an hour rather than several days of direct integration.
Use Jentic search for 'check the spam score of a phone number', load the /api/v1/spam-score schema, and execute it with the inbound phone number.
Key Endpoints
14 endpoints — jentic publishes the only available openapi specification for callerapi, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/v1/spam-score
Get spam score and HLR data for a number
GET
/api/v1/kyc
Run a phone-based KYC check
GET
/api/v1/ported-date
Get the last ported date of a number
GET
/api/v1/porting-history
Retrieve full porting history
GET
/api/v1/online-presence
Check messaging and social online presence
POST
/api/v1/webhooks/subscribe
Subscribe to daily spam report webhooks
POST
/api/v1/upload/contacts
Upload contacts for batch enrichment
GET
/api/v1/account/balance
Check remaining account credits
GET
/api/v1/spam-score
Get spam score and HLR data for a number
GET
/api/v1/kyc
Run a phone-based KYC check
GET
/api/v1/ported-date
Get the last ported date of a number
GET
/api/v1/porting-history
Retrieve full porting history
GET
/api/v1/online-presence
Check messaging and social online presence
POST
/api/v1/webhooks/subscribe
Subscribe to daily spam report webhooks
POST
/api/v1/upload/contacts
Upload contacts for batch enrichment
GET
/api/v1/account/balance
Check remaining account credits
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The CallerAPI x-api-key header value is stored encrypted in the Jentic vault. Agents call spam-score, kyc, and webhook operations by name and Jentic injects the header at execution time — the raw key never enters the agent prompt or logs.
Intent-based discovery
Agents search Jentic by intent (for example 'check the spam score of a phone number' or 'subscribe to daily spam reports') and Jentic returns the matching CallerAPI operation along with its input schema, so the agent can call the right endpoint without browsing CallerAPI documentation.
Time to first call
Direct CallerAPI integration: 1-2 days for x-api-key wiring, webhook subscription handling, and credit accounting. Through Jentic: under 1 hour — search for the operation, load its schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CallerAPI API through Jentic.
Why is there no official OpenAPI spec for CallerAPI?
CallerAPI publishes API documentation at docs.callerapi.com but does not host a downloadable OpenAPI specification on a developer portal. Jentic generates and maintains this spec so that AI agents and developers can call CallerAPI via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does CallerAPI use?
CallerAPI uses an API key passed in the x-api-key HTTP header on every request. Through Jentic, the key is stored encrypted in the credential vault and injected at execution time, so the agent never holds the raw value.
Can I get HLR carrier data for a phone number with CallerAPI?
Yes. The /api/v1/spam-score endpoint returns the spam score together with HLR (Home Location Register) carrier data and basic line type information in a single response, so a number lookup does not need to be split across two calls.
What are the rate limits for CallerAPI?
Rate limits are not declared in the OpenAPI specification. CallerAPI uses a credit-based model — call /api/v1/account/balance to check remaining credits before scheduling large batches of lookups, since each lookup type consumes a different credit cost.
How do I subscribe to daily spam reports through Jentic?
Run a Jentic search for 'subscribe to daily spam reports', load the /api/v1/webhooks/subscribe schema, and execute it with the receiver URL. Then load and execute the /api/v1/webhooks/test schema to verify the receiver is reachable. Install the SDK with pip install jentic and use the async search, load, and execute pattern.
Is CallerAPI free?
CallerAPI prices lookups per credit rather than offering a free tier, and different lookup types consume different credit amounts. Pricing is set by CallerAPI and is not declared in the OpenAPI spec — refer to docs.callerapi.com for the current per-lookup cost.
GET STARTED