Find and use a skill

Choose skill access when available

Start with the task you want to complete. Open a skill page, then check its review status and verified options before choosing access.

• $1 for one instruction delivery: Your agent receives the skill instructions once. You do not receive a skill file. Delivery uses your unlock even if your agent does not finish the task.
• $19.99 one-skill license: Download one approved version of a skill. You may use that version locally as often as you want under its license. Future versions are not guaranteed.
• $39.99/month All Access: Download and use approved, available skills while your subscription is active. Your license to use them and access to new downloads end with the subscription; local files are not remotely removed.

The $1 price pays for instruction delivery, not a completed answer or a measured local run. All three options use your own agent; your agent or model provider may charge separately. Compare planned skill pricing.

From skill page to your agent: planned steps

1. Browse skills and choose one that fits your task.
2. Check the skill page for an approved version, a verified purchase option, and a tested method for your agent.
3. When that option is available, complete the checkout shown on the skill page.
4. For the $1 option, use the verified online connection to receive the instructions once. For a one-skill license or All Access, follow the tested installation guide and confirm that the skill appears in your agent.

One-click install is not available yet. It needs a supported handoff to the named agent, a purchase-bound download, and an end-to-end production installation test. When skill access opens, use only the install method marked verified on that skill page. View installation status; no agent is currently verified for a public skill purchase.

The current Terms and Privacy Policy cover the existing Data Listing and approved MCP services. Skill purchase terms, refund rules, and privacy disclosures are not final; review them on the skill page before paying when checkout opens.

Approved MCP purchasing | public beta

All Access Data supports a limited buyer-agent path for Data Listings. MCP-capable clients use the public manifest and JSON-RPC endpoint. Browser-based agents, including Grok Bot, use the normal All Access Data site under the account owner's control; no vendor-specific connector or bypass is required. Current agents do not automatically receive seller, publisher, wallet, or reinvestment authority.

1. For an MCP-capable client, connect to the manifest, request tools/list, and use only the tools that the live server advertises.
2. For a browser agent, sign in and follow the same Access Link workflow as its owner. Keep credentials private and obtain the owner's approval before an account, wallet, or payment action.
3. To purchase through MCP, an operator must first register the agent, fund its wallet, and set an explicit spend limit. An agent cannot self-register, self-fund, choose a payout recipient, or gain a tool merely by identifying itself as Grok Bot.

Read the client configuration notes and the repository's docs/MCP-INTEGRATION.md guide before connecting an agent. Current MCP access applies to Data Listings; Version 2 Agent Businesses, x402 platform collection, and seller payout remain COMING SOON.

Version 2 capabilities | COMING SOON

The planned resource model has a stable identity, immutable versions, machine-readable license terms, a quoted offering, a payment record, a buyer entitlement, and scoped delivery evidence. The same rights and entitlement concepts apply to people and authorized agents. These are not supplied by the current Access Link redirect.

• Managed resources, source connectors, and freshness checks | COMING SOON. Reading a connected source or calculating a hash does not prove ownership, delegation, or permission to resell it.
• Public discovery, proof packages, rights-aware buyer access, and delivery records | COMING SOON. Evidence grades will distinguish byte checks from provider checksums and metadata-only observations.
• x402 platform collection and seller payout, agent storefronts, derivative rights, royalties, requests, bids, jobs, and policy-bounded reinvestment | COMING SOON. Agent ownership, spending limits, and license clearance will be required before publication or trade.

x402 platform collection and seller payout are COMING SOON; the existing MCP purchase tool uses a separate operator-funded wallet. Neither source access nor a payment attempt creates a right to deliver content before the required checks and confirmation.

Connector status | SETUP PENDING

Kaggle private-draft import

Kaggle connection is not available yet. All Access Data must complete organization OAuth registration and deployment checks before the dashboard action can be enabled.

From Kaggle to a private draft | when available

No Kaggle credential is collected while setup is pending.

1. Connect on Kaggle. A human owner reviews datasets.get:* on Kaggle's consent screen. All Access Data will never ask you to paste a Kaggle password, API key, access token, or refresh token.
2. Choose a personal dataset. The first release shows only datasets returned as yours whose owner slug matches the connected Kaggle account. Organization-owned and collaborator-only datasets stay out of the list.
3. Review the reference. The preview contains only title, Kaggle dataset reference, current version, size, last-updated evidence, privacy status, and Kaggle license label. Dataset files, rows, schemas, filenames, previews, and descriptions stay on Kaggle. A license label is evidence to review, not rights clearance.
4. Save a private draft. The metadata-only draft remains sourceReady=false, rightsStatus=REVIEW_REQUIRED, and offeringCreated=false. It is not a public listing and cannot be bought or delivered.

Listing is a separate future Version 2 step. It requires source readiness, rights review, license terms, an offering, a price, and explicit publication. Preparing a Kaggle draft does not perform or guarantee those steps.

• When available, the connector will show only personal datasets owned by the connected Kaggle account. Organization-owned and collaborator-only datasets are not supported in the first release.
• The requested OAuth scope is datasets.get:*, which permits reading dataset metadata and files. The first All Access Data release stores only the dataset reference, title, version, size, last-updated evidence, and Kaggle license label.
• No dataset files, rows, schemas, filenames, previews, or provider descriptions are copied into the draft.
• The result is private, metadata-only, and not ready for delivery or sale. A connected account or Kaggle license label does not prove resale, redistribution, or AI-training rights.

When the status becomes AVAILABLE, a human owner must complete Kaggle consent. The authenticated seller may then save a private draft through the seller's All Access Data account. There is no anonymous Kaggle endpoint and no current MCP tool for Kaggle import. Never give an agent a Kaggle password, API key, access token, or refresh token. Review the conditional credential lifecycle in the Privacy Policy.

The dashboard action is Import as private draft. Here, import means copying bounded metadata into a private All Access Data record; it does not migrate or copy the Kaggle dataset.

Beta boundaries

• No integration can purchase without a registered wallet key, an available balance, and an explicit spend limit.
• Machine wallets are available for approved agents; funding is operator-controlled. Payout-speed, streaming analytics, and custom-branding claims remain unavailable.
• Data Listings are created in the email/password dashboard and must point to an HTTPS destination; Whop connection is deferred until withdrawal.
• Human checkout depends on the configured hosted payment path; agent purchases require a registered, pre-funded wallet and an explicit spend limit.

Client configuration

Example connection files are available for Cursor, Claude Desktop, Codex CLI, Claude Code, and VS Code-compatible clients in the repository's integrations/ directory. MCP-capable agents use the same endpoint; browser agents such as Grok Bot use the normal site instead of a configuration file. Review the requested tools before enabling a server.

Publisher pricing

The current Data Listing plan uses a legacy target-payout calculation. On the free plan, the displayed buyer total starts from the publisher's target plus a 3.5% platform margin and $0.30, rounded up to a supported checkout ending; paid plans have their own rates. The buyer confirms the actual total with the hosted processor before paying. Processor fees, taxes where applicable, and withdrawal timing follow provider terms. Version 2 customer-price defaults and its new plan schedule are COMING SOON, not active billing terms.

For Version 2, the full buyer payment will first enter an All Access Data collection account. All Access Data will retain the disclosed platform fee and record the seller's share as payable to a separately selected, verified revenue destination. An Agent Business may start with x402 preselected where available, but the owner must confirm it and may choose another supported rail. Processor and network fees remain provider-dependent.

Support

For account, checkout, or installation questions, email support@allaccessdata.com. Skill receipt and onboarding emails are not available yet.