canonical: https://jentic.com/apis/getlinkintel.com/getlinkintel # Getlinkintel LinkIntel API The LinkIntel API gives an AI assistant evidence for its next X post: the customer's own recent X posts once they connect their X account, X's published ranking weights and their changelog, and optional public posts they choose, returned as a cited content brief. It exposes a JSON-RPC endpoint that agent tooling calls to discover and run those operations, plus an ingest endpoint that registers newly published posts for measurement. The ranking-weights endpoint surfaces how X currently scores content so a brief can be grounded in the live algorithm. It is aimed at creators and growth tools that want post suggestions backed by real ranking signals rather than guesswork. ## For AI agents Gather evidence for the next X post: register published posts for measurement, read X's published ranking weights and changelog, and return a cited content brief grounded in real ranking signals. ## Scope Does not publish posts, schedule content, or manage ad spend. Use for gathering X ranking signals and post-performance evidence for content briefs only. ## Capabilities - Register newly published posts so their performance can be measured - Read X's published ranking weights and the changelog of how they shift - Return a cited content brief that grounds a post suggestion in ranking signals - Pull the customer's own recent X posts once they connect their account - Run operations through a JSON-RPC endpoint that agent tooling discovers on demand ## Use cases ### Agent-written content brief An AI writing assistant can call the LinkIntel API through Jentic to read X's current ranking weights and the customer's recent posts, then return a cited content brief for the next post. Jentic returns the right operation from a natural-language query, so the assistant grounds its suggestion in live ranking signals without parsing the LinkIntel reference first. Example prompt: Read X's published ranking weights, pull the customer's recent posts, and return a cited content brief recommending what to post next. ### Post performance measurement Register newly published posts through the ingest endpoint so their performance can be measured against the ranking weights over time. Automation tools use this to close the loop between what was posted and how the algorithm scored it. Example prompt: Register the posts published in the last day through the ingest endpoint and confirm how many were accepted for measurement. ### Ranking-weight monitoring Read X's published ranking weights and their changelog to track how the algorithm's priorities move, which is a public endpoint so a dashboard can poll it without a connected account. Teams use this to adjust content strategy as the weights change. Example prompt: Read the current ranking weights and their changelog, then report which signals gained the most weight since the last check. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/mcp` | Send a JSON-RPC message to the server | | GET | `/x-algorithm.json` | Retrieve X's published ranking weights and changelog | | POST | `/api/ingest/posts` | Register published posts for measurement | | GET | `/api/ingest/posts` | Describe the ingest endpoint | ## Key resources - **Signals** — Read X's published ranking weights and their changelog - **Ingest** — Register newly published posts for measurement and describe the ingest endpoint - **Brief** — Return a cited content brief through the JSON-RPC endpoint ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 68 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 90 / 100 - Developer Experience & Jentic Compatibility: 65 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 94 / 100 - Security: 70 / 100 - AI Discoverability: 72 / 100 - **View full report:** https://jentic.com/apis/getlinkintel.com/getlinkintel/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the LinkIntel API by hand means running the OAuth2 flow to connect an X account, handling bearer tokens for the JSON-RPC and ingest endpoints, and coding each call yourself. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The LinkIntel endpoints carry no resource id in the URL path, so bound your agent to the operations it needs, such as reading ranking weights and recent posts. You choose which operations it may call, so the ingest operation is not included unless you add it. - **Credential handling:** Your LinkIntel token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get a content brief' or 'read X ranking weights', and Jentic returns the matching LinkIntel operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Mention API** — Social listening across mentions and sentiment - **Twitter API v2** — Official X platform API for posts and engagement data - **Buffer API** — Schedule and publish social posts across platforms ## FAQ ### Is there a LinkIntel API MCP server? Yes. LinkIntel exposes a JSON-RPC endpoint that MCP clients can call directly. You can also connect it through Jentic from the API Directory: your agent gets the full four-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call. ### What authentication does the LinkIntel API use? The API uses OAuth2 authorization code to connect a customer's X account and bearer tokens for the JSON-RPC and ingest endpoints, per its OpenAPI spec. Through Jentic the token is stored encrypted in your own Jentic One instance and supplied only when an allowed call runs, so it never reaches the agent's context. ### Can I read X's ranking weights with the LinkIntel API? Yes. The ranking-weights endpoint returns X's published weights and their changelog, and it is a public endpoint, so a dashboard can poll it without a connected X account. The weights are what a content brief grounds its suggestions on. ### What are the rate limits for the LinkIntel API? The OpenAPI spec does not specify rate limits. The service is priced per month rather than per request, so confirm the limits for your plan in the LinkIntel documentation at https://www.getlinkintel.com/pricing.md. ### Can I limit what my agent is allowed to do with the LinkIntel API? Yes. Write a rule that permits only the read operations, pulling ranking weights and recent posts, when the agent should only draft briefs, and add the ingest operation only for workflows that register published posts, with every call logged. ### How do I get a content brief with the LinkIntel API through Jentic? Search Jentic for 'get a content brief for my next X post' to surface the brief operation, load its input schema, pass the connected account context, and execute. To run it on your own infrastructure, install Jentic One from its GitHub repo.