PREDIK Data-Driven

PREDIK Location Intelligence & Foot Traffic Data API

Partner-delivered, contact-sales data API that serves PREDIK's enriched location-intelligence products - POI data, aggregated foot-traffic and mobility data, company and commercial-area intelligence, and socio-demographic enrichment. PREDIK lists REST API, SOAP API, and Feed API (alongside S3-bucket) as delivery channels, with output in JSON, CSV, or SQL. Access, schema, and coverage are negotiated per engagement. The API host itself was verified live on 2026-08-14 - https://api.predikdata.com is an AWS API Gateway custom domain on PREDIK's own domain (TLS cert CN=*.predikdata.com issued by Amazon), and its /ping endpoint returns HTTP 200 "Healthy Connection". Every other probed path returns the API Gateway 403 {"message":"Missing Authentication Token"}, so the routes and the contract are entirely credentialed. No public developer portal, API reference, authentication documentation, or machine-readable specification is published anywhere, and the provider's own llms.txt (a complete inventory of every page on predikdata.com) lists no developer or documentation page at all. Endpoints are therefore not modeled (endpointsModeled=false) - the host is real and reachable, but nothing about its surface is publicly described.

GitHub

Documentation

📖
Documentation
https://predikdata.com/location-intelligence-solutions/

Other Resources

🔗
Listing
https://datarade.ai/data-providers/centralamericadata/profile
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/predikt-ai/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/predikt-ai-location-intelligence-data-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: predikt-ai:predikt-ai-location-intelligence-data-api
name: PREDIK Location Intelligence & Foot Traffic Data API
tags:
- Location Intelligence
- Foot Traffic
- POI Data
- Data Enrichment
- Web Intelligence
- Company Data
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://predikdata.com/location-intelligence-solutions/
baseURL: https://api.predikdata.com
properties:
- url: https://predikdata.com/location-intelligence-solutions/
  type: Documentation
- url: https://datarade.ai/data-providers/centralamericadata/profile
  type: Listing
description: Partner-delivered, contact-sales data API that serves PREDIK's enriched location-intelligence
  products - POI data, aggregated foot-traffic and mobility data, company and commercial-area intelligence,
  and socio-demographic enrichment. PREDIK lists REST API, SOAP API, and Feed API (alongside S3-bucket)
  as delivery channels, with output in JSON, CSV, or SQL. Access, schema, and coverage are negotiated
  per engagement. The API host itself was verified live on 2026-08-14 - https://api.predikdata.com is
  an AWS API Gateway custom domain on PREDIK's own domain (TLS cert CN=*.predikdata.com issued by Amazon),
  and its /ping endpoint returns HTTP 200 "Healthy Connection". Every other probed path returns the API
  Gateway 403 {"message":"Missing Authentication Token"}, so the routes and the contract are entirely
  credentialed. No public developer portal, API reference, authentication documentation, or machine-readable
  specification is published anywhere, and the provider's own llms.txt (a complete inventory of every
  page on predikdata.com) lists no developer or documentation page at all. Endpoints are therefore not
  modeled (endpointsModeled=false) - the host is real and reachable, but nothing about its surface is
  publicly described.