What the API does and who it is for
Caller ID & Social Search (Eyecon) resolves a phone number into identity data — specifically the name associated with that number, a linked Facebook ID, a public profile URL, and a current profile picture. It also flags numbers that have been reported as spam. That combination of identity resolution and social enrichment sets it apart from basic reverse-lookup services that return only a name or carrier.
The API targets a fairly broad developer audience: anyone who needs to attach a human identity to a raw phone number. That covers mobile app developers building caller ID screens, backend engineers enriching CRM records, and security teams cross-referencing phone numbers against known identities. At ~997 ms average latency, responses are not instantaneous, so real-time caller ID overlays are feasible but not blazing fast — factor that into any UI that shows results before a call connects.
The reported 90% success rate is worth keeping front of mind during evaluation. One in ten requests may return incomplete or empty results, which is typical for reverse-lookup services that rely on crowdsourced and social-graph data rather than a fully licensed telco database. Design your integration to handle graceful fallbacks.
Endpoint walkthrough
Caller ID & Social Search (Eyecon) exposes four GET endpoints across two functional groups.
Identity lookup
- GET /search — The primary search endpoint. Submit a phone number and receive name, Facebook ID, and image URL in the response.
- GET / — A root-path variant of the same lookup. Both endpoints return identical fields, so you can treat
/searchas the canonical choice and use/as an alternative if your routing layer has constraints.
Both endpoints support GET and POST requests, giving you flexibility in how you pass the phone number parameter — as a query string or in a request body.
Image lookup
- GET /image_lookup.php — Returns the profile image associated with a phone number directly.
- GET /image — A cleaner-path version of the same image lookup.
Having dedicated image endpoints is useful when you only need the photo — for example, populating an avatar in a contacts UI — without parsing a full JSON response for the other fields.
Pricing breakdown
The API follows a freemium model. All paid tiers cap the request rate at 5 requests per second.
| Plan | Price | Monthly requests | Image lookups | Rate limit |
|---|---|---|---|---|
| BASIC | $0 | 5 | 5 | — |
| PRO | $7 | 1,500 | 1,500 | 5 / sec |
| ULTRA (recommended) | $70 | 30,000 | 30,000 | 5 / sec |
| MEGA | $200 | 100,000 | 100,000 | 5 / sec |
The BASIC tier's five monthly requests are genuinely only useful for testing an integration end-to-end — you will exhaust them in a single smoke-test session. Do not plan a production feature around the free tier.
PRO at $7/month covers 1,500 lookups, which works out to roughly 50 lookups per day. That is reasonable for a small internal tool, a low-volume CRM enrichment job, or a side project. At 5 req/s, the rate cap will not be a bottleneck at this volume.
ULTRA at $70/month (the provider-recommended tier) offers 30,000 monthly requests — about 1,000 per day. The cost per lookup drops significantly compared to PRO: approximately $0.0023 versus $0.0047. If your anticipated volume is anywhere near 1,500/month, it is worth modelling whether ULTRA delivers better cost efficiency even at a higher flat fee.
MEGA at $200/month supports up to 100,000 requests, keeping the rate cap constant at 5 req/s. At 5 req/s sustained, you could theoretically exhaust 100,000 requests in under six hours, so the monthly quota rather than the rate limit is the binding constraint at this tier.
Practical use cases
Caller ID applications. Submit the incoming call's number to /search and display the resolved name and photo before the user answers. At ~1 second latency, triggering the lookup the moment the ringing event fires gives you enough time to surface a result.
CRM enrichment. When a new contact record is created with only a phone number, fire a background job against the API to fill in the name and profile picture automatically. This is a good fit for the PRO or ULTRA tier depending on your contact ingest volume.
Lead validation. Before routing a sales lead, verify that the submitted phone number resolves to a real identity and is not flagged as spam. The spam detection field alone can help filter bot-submitted forms.
Fraud screening. Cross-reference a phone number provided during account registration against the returned identity. A mismatch between the stated name and the API-returned name, or a spam flag, can feed into a risk-scoring model.
Customer support automation. Match an inbound support call to an existing customer record by phone number before the agent picks up, reducing handle time.
Limitations and things to check before integrating
Coverage depends on data availability. Results are tied to whether the number has a linked Facebook presence or is present in Eyecon's crowdsourced database. Numbers in regions with lower Facebook penetration or limited Eyecon user bases may return empty results more often than the 90% average suggests.
Single rate limit across tiers. Paid plans share a 5 req/s ceiling. If you need burst throughput beyond that — for example, a bulk enrichment job — you will need to queue requests client-side. No higher rate limit tier is available even at the MEGA level.
Privacy and compliance. Reverse lookup and social data enrichment intersects with privacy regulations in many jurisdictions (GDPR, CCPA, and others). Verify that your use case and the data returned are compliant with applicable rules before going to production, particularly if you are storing or displaying the resolved names and photos.
No mention of international coverage scope. The documentation does not specify which countries or number formats are supported. Test with the phone number formats relevant to your market on the BASIC tier before committing to a paid plan.
Getting started
Sign up on the marketplace and activate the BASIC plan to get your API key at no cost. Run a few test calls against GET /search with known phone numbers in your target market to validate coverage and response quality before upgrading. Because both the identity and image lookup endpoints share the same monthly quota, decide early whether you will call them independently or consolidate on the combined /search response to avoid double-counting requests. Once you are satisfied with coverage, choose the paid tier that matches your projected monthly lookup volume — and budget in the ~10% failure rate when sizing that volume estimate.
