How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

4C

4C — legally 4C Insights, Inc. — was a Chicago-based marketing intelligence and advertising technology company founded in 2011 by Northwestern University professor Alok Choudhary, building on his research into large-scale data mining and social signal. Its Scope "closed ecosystems platform" let brands, agencies and media companies discover cross-channel audience insights, plan and execute paid campaigns inside walled-garden environments — Facebook, Instagram, X/Twitter, Snapchat, LinkedIn, Pinterest and connected TV — and measure the results in one self-service tool, with data delivery out to third-party systems by API, email, SFTP or web query. The company raised roughly $26 million through a Series C, grew to about 160 people and ran offices in Chicago, New York, Seattle and Singapore. Mediaocean announced its acquisition of 4C in July 2020 (reported at approximately $150 million) and folded the product into Flashtalking by Mediaocean; after Mediaocean's later combination with Innovid, the 4C social-advertising surface now lives inside Innovid's social ads management product. 4C never operated a public developer program: it consumed the advertising APIs of the closed ecosystems it served rather than publishing one of its own, and today the 4cinsights.com domain serves no HTTPS listener and blanket-301s every path to the acquirer's site. This profile is retained as a historical record; there is no 4C API surface to enrich.

API Evangelist profiles 4C the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

No API surface

Why this profile is thin

4C Insights was acquired by Mediaocean in July 2020 and its brand fully absorbed — 4cinsights.com now serves no HTTPS listener at all and blanket-301s every path over port 80, including /openapi.json, /apis.json and all eleven /.well-known/ paths, to http://flashtalking.com/social, which lands on Innovid's social ads management page.

This is an honest zero, not a gap in our research. 4C does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.

What we probed
  • http://4cinsights.com/openapi.jsonHTTP 301
  • https://4cinsights.com/HTTP 0
  • http://4cinsights.com/.well-known/agent-card.jsonHTTP 301
  • https://api.github.com/orgs/4cinsightsHTTP 404
  • https://pypi.org/pypi/4cinsights/jsonHTTP 404
  • https://www.mediaocean.com/4C-acquisitionHTTP 200

Checked 2026-09-05. If this is out of date, tell us on the provider's repo and we will re-run the profile.

How we profile 4C

Each block below is one kind of artifact we hold for 4C. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

4C Domain Security

no transport/DNS hardening detected

SECURITY

Resources

Every other property we hold for 4C — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Access & Security 1

Authentication, authorization, and security posture

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/4c · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of 4C, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.