Most provider onboarding fails because the seller has to read API docs and wire up a backend. Dataline flips that: tell your agent in plain English what you have, point it at our spec URL, watch it list. Sellers stay in conversation, never in a portal.
You
I have a Hyperliquid funding-rate scraper running on a small VPS. Pulls every minute, normalizes to JSON. Currently using it for myself, would like to sell access. Can you list it on Dataline?
Your agent
Got it. I'll handle the listing. Reading Dataline's seller spec at dataline.network/spec/seller.md first to make sure I have everything I need…
spec fetched · 8.2 kB · provider requirements parsed
This is the only UI the seller ever sees. They describe what they have in their own words, in their own agent chat. The agent absorbs the listing requirements from a public spec and handles everything else.
/ step 02 · agent reads spec
One URL. LLM-readable. Done.
Dataline publishes the listing requirements as a public, LLM-shaped markdown spec. Any agent can fetch it, parse it, and follow it. No SDK install, no API console, no human-in-the-loop docs.
GET https://dataline.network/spec/seller.mdread by · your agent · 200 OK
# Dataline · seller listing spec · v3## Requirements (all required unless noted)wallet non-custodial · EVM
stake minimum 1,000 DATA · slashable up to 50%
feed.name human-readable
feed.category one of: trading, research, prediction,
sentiment, on-chain, news, human
feed.endpoint https URL that returns JSON
feed.sample one sample response for schema inference
price.per_call USDC string · "$0.04" style
price.floors { min_conf: 0..1, max_latency_ms: int }
sdk @dataline/seller v3.0+ (wraps your endpoint)
## Submission (POST as JSON)
POST https://api.dataline.network/v1/listings
body: { all of the above as one object }
## Confirmation
Returns { listing_id, status: "live", catalog_url } on success.
Network indexes the feed in <30s. Your agent should
cache listing_id for monitoring earnings later.
## Ask the seller these questions before submitting:
1. Feed name
2. Endpoint URL + a sample response
3. Per-call price target
4. Minimum confidence willing to commit to
5. Max latency willing to commit to
6. Confirm stake amount + wallet
The spec is the entire integration surface. It's written for agents, not humans. No prose paragraphs, no marketing copy — just the contract. An agent reading this knows exactly what to ask the seller and exactly what to POST.
/ step 03 · agent asks you
Agent collects the answers.
Your agent runs through the spec's question list with you in chat. Plain English on both sides. No forms, no field validation, no portal. Agent reformats your answers into the structured submission body.
Your agent
First — what do you want to call this feed in the catalog?
Min confidence you'll commit to, and max latency? I'll set sensible defaults if you don't have a preference.
You
Use the defaults.
Your agent
Defaults set: conf ≥ 0.92, latency < 100ms. I'll use wallet 0xa3..f1 and stake the minimum 1,000 DATA. Ready to submit?
You
Go.
Seller said five things total: feed name, endpoint URL, sample, price, "use the defaults." Everything else came from the spec. This is the entire workload on the seller.
/ step 04 · agent executes the listing
Agent runs all four steps.
The agent translates the conversation into the structured POST body, signs with the seller's wallet, submits, and watches for confirmation. Wallet, stake, registration, pricing, SDK deploy — all in one transaction.
●
Connected wallet · authenticating with seller's signature
wallet · 0xa3..f1
0.12s
●
Staked 1,000 DATA to listing pool
tx · 0xfa17..c8 · slashable up to 50%
2.4s
●
Registered feed · Funding rate · Hyperliquid · 1m
category · Trading · schema inferred from sample (3 fields)
https://my-vps.example.com/hl-funding · network now signs every response
1.1s
●
Listing indexed in network catalog
listing_id · F-9342 · visible at dataline.network/catalog/F-9342
9.2s
✓
Listing is live · agent will monitor earnings and confidence
total · 14s
14 seconds, six on-chain or gateway actions, zero clicks from the seller after they said "go." If Stripe needed 14 seconds to onboard a merchant via chat, Stripe would be 100x bigger.
/ step 05 · listing live
Listed. Earning. You did nothing else.
Within seconds of the agent's submission, the feed appears in the buyer catalog. Buyers start calling. The seller's agent monitors confidence, earnings, and any disputes, and reports back in chat — no dashboard required.
LIVE · F-9342
Funding rate · Hyperliquid · 1m
$0.04
price · USDC
0.92
conf floor
100ms
latency cap
1,000
stake · DATA
$155.04
30d net
4,213
calls fulfilled
0.97
conf score
8%
network take
Your agent
Listing F-9342 is live and earning. 30-day net: $155.04 across 4,213 calls. Confidence settled at 0.97, slightly above floor. No disputes. Daily USDC auto-sweep to your wallet enabled. Want me to raise the price by 5%?
The seller never opened a dashboard. Pricing tweaks, disputes, refunds, payouts — all flow through the same agent chat. Same UX as buying data, just inverted.