Skip to main content
The original four profile operations passed in the native Grok Bot app on October 17, 2026 using a private local REST skill. Its Datalayer MCP/OAuth route remains unverified. Grok web and external xAI API calls are separate paths; this guide is for the native app.
1

Prepare a dedicated key

Open Connections in Datalayer. Reuse an existing Datalayer integration and its protected key. For a new setup, create a dedicated API key named Grok Bot so you can revoke it separately.
2

Ask Grok Bot to create the private skill

Copy the setup prompt below into Grok Bot. It contains no secret. Keep the API key out of chat, generated source, URLs, logs and shared repositories.
3

Configure protected credential storage

Supply the key only through protected local credential storage, following the private credential setup in your app. If no secure entry is available, stop instead of pasting the key into chat.
4

Check authentication only

Have Grok Bot run GET /v1/auth first. It should return {"authenticated":true}. This check uses no credits and makes no data lookup. Confirm the data operations and get_account_details are available before requesting research.

Paste this

Copy this into Grok Bot. It contains no secret. The same prompt is on Get started. If Grok Bot needs every field bound, use the full operation list below. Keep the key out of chat and skill source.

Full operation list

This is a private custom setup, not a marketplace listing. The OpenAPI specification is the field reference. For a company lookup by domain, supply only the hostname, such as stripe.com, without a scheme or path. Omit absent optional fields instead of sending null. Once authentication succeeds and your account has an active allowance, copy:
On the published plan for new signups, a search with results costs 1 credit and an empty search costs nothing. A new profile costs 1 credit, and a verified work email costs 2. All clients share the same allowance. Review usage and saved results in your dashboard. Do not interpret a timed-out search as no matching records; follow usage and retries. Custom skills depend on your account and team policy. If protected credential storage is unavailable, stop setup and use dashboard Support. See Grok Bot’s app and plugin guide. Revoke the dedicated API key in Connections when removing this integration. The October 17 acceptance above covers the original four operations. It does not by itself verify this expanded credit release in the installed client. Saved connections keep their existing names.