Evidence-backed social intelligence for AI agents.

Turn Social/X and public-web signals into structured, traceable insights with sources, confidence, and uncertainty.

Explore the APIConnect via MCP

No wallet custody. No marketplace. No raw social-data resale.

Intelligence Contract

Choose a transport example
46/500
Derived insight

Adoption is rising, while reliability and permission controls remain common blockers.

Confidence0.84
Sources required3 domains
Uncertainty includedPlain-language rationale

Sources (3)

x.comSocial/Xgithub.comDeveloper forumsdev.toDeveloper blogs

Response (structured)

{
  "content": [{ "type": "text", "text": "Evidence-backed insight" }],
  "confidence": 0.84,
  "uncertainty": "Coverage skews to English-language sources."
}
{
  "sources": ["x.com", "github.com", "dev.to"],
  "confidence": 0.84,
  "uncertainty": "Coverage skews to English-language sources."
}

Choose how you pay

Same APIs. Same evidence contract. Choose the billing model that fits the caller.

Monthly subscription

Card or bank

Predictable spend for developers and teams.

View plansPlanned

Pay per call

Machine-native via x402

$0.01–$0.10 per call

For autonomous agents and variable usage.

Use pay per callPaused

Four evidence-backed tools

Start with focused Social/X intelligence today; the contract is designed for additional public-web and data providers over time.

$0.01 / call

search_social

Search and normalize up to 25 recent public X signals.

REST: POST /v1/search/social
Credit budget: 20 default / 25 max

$0.02 / call

user_intelligence

Evidence-backed intelligence for one public X account.

REST: POST /v1/intelligence/user
Credit budget: 40 default / 50 max

$0.05 / call

topic_intelligence

Trends, themes, controversies, and sources for one topic.

REST: POST /v1/intelligence/topic
Credit budget: 80 default / 100 max

$0.10 / call

product_intelligence

Evidence-backed product feedback, pain points, and competitor signals.

REST: POST /v1/intelligence/product
Credit budget: 120 default / 150 max

Provider-agnostic by contract

MCP and REST return the same structured result regardless of billing model. Payment authorization stays separate from evidence generation.

Current data boundary

The current bridge retrieves public X data through Xquik Guest REST. Evidexa sells derived intelligence and evidence, not raw social data. Xquik is the MVP's single upstream fault domain. Results may be partial or no_data, and raw post text is not mirrored in responses.

REST quickstart

curl -i https://evidexa.okmybot.com/v1/search/social \
  -H 'content-type: application/json' \
  -d '{"query":"x402 agent payments"}'

Paid execution currently returns HTTP 503 EVIDEXA-503-PAID_ACCESS_PAUSED without a payment challenge or charge. See Docs for the complete contract.