Documentation

Quickstart

1. Upload or paste a table. Review the inferred fields and human view.
2. Choose access and publish. Share publicly, require an API key, or configure paid access with Pro.
3. Give your agent /llms.txt. It links the contract and explains focused queries.

Use this data for current reference tasks. Read its instructions first:
https://data.ddigger.ai/t/{tenant}/d/{source}/llms.txt

Connect your agents

1. Publish your source, then copy its agent instructions from Publish.
2. Use an agent or workflow with an HTTP request tool. A URL alone does not install a connector or give a chat application network access.
3. For key-protected data, configure the API key in your tool's secret storage and send it in the Authorization header. Do not paste the key into a chat or public URL.
4. Ask the agent to read the instructions and schema, then request a few rows. Verify a successful response, the expected rows, and the X-DDigger-Version response header in your tool.

Republishing keeps the latest URLs stable. Public CSV and Google Sheets URL sources can be checked daily for changes after you enable refresh in Data; this is not instant synchronization. The API is read-only.

Sell access to your data

Prepare a draft for free. Publishing paid access requires Pro. Your ddigger subscription is separate from what buyers pay for your data.

1. In Access, select Paid, choose the payment scope, and enter your price and Tempo payout wallet.
2. Review the access terms before publishing. Published paid addresses cannot switch to public or key-protected access.
3. Share the published instructions with your buyers. They need a client supporting the Machine Payments Protocol (MPP) with Tempo payments and a funded wallet; this is not a card checkout.
4. The client follows the HTTP 402 challenge and retries with a payment credential. Follow the source's generated instructions and OpenAPI contract for subsequent requests and recovery.
5. Confirm the buyer's payment and successful data response. Opening a link or copying instructions does not prove that payment or access succeeded.

Payments settle directly to your payout wallet. ddigger provides the paid-access endpoint, not a buyer marketplace or a guarantee of sales. Only publish data you have the right to distribute.

Query the data

Start with /llms.txt. Request only the rows and fields the task needs.

curl

curl 'https://data.ddigger.ai/t/{tenant}/d/{source}/data?fields=city,country&where=region:eq:Europe&limit=10'

JavaScript

const rows = await fetch(sourceUrl + '/data?limit=10').then(r => r.json());

Python

import json, urllib.request
rows = json.load(urllib.request.urlopen(source_url + '/data?limit=10'))

Agent endpoints

/llms.txt

Instructions, field descriptions, query rules, and links to the other endpoints.

/openapi.json

An OpenAPI 3.1 contract with field-specific operators and values.

/data

The latest dataset. Add query parameters to request only the rows and fields you need.

Focused queries

Use fields, repeated where parameters combined with AND, limit, and offset.

GET /data?fields=country,capital&where=region:eq:Europe%20%26%20Central%20Asia&limit=10

Supported operators are eq, ne, gt, gte, lt, lte, and contains. Check each dataset's OpenAPI contract for the operators supported by each field.

Versions and access

Latest URLs move when you republish. Pinned /v/{version} URLs preserve an exact retained version. Private datasets require Authorization: Bearer <api key>.

Live example

Inspect sourced World Bank country metadata before publishing your own data. Follow the CSV-to-API guide to see the steps from a file to a published source.