Desk workflow: export the shortlist and request Data API access

A Breakflare data API mid-cap export is the step a desk takes after the daily habit already works on the dashboard, not before. Breakflare is a daily hype-momentum attention tracker for CoinGecko ranks 51-500. It scores hype, 3d/7d momentum, Climb, Breakout Index™, and confidence. Plus gives you the live board. The Data API and Datasets are separate, access-by-request products for teams that need those same fields inside their own systems.

Key Takeaways

• Plus is the right home for the daily sort, starring, alerts, and review. Prove that loop for several weeks before you ask for files or keys.
• The Data API is not part of Plus. It is a separate product with its own manual review, and keys are not issued with a dashboard plan.
• Request access when you can name the system that will consume the fields, how often it will read them, and who owns the process.
• The request form is a use-case review, not a checkout. Rates are shared privately after approval.
• Breakflare is an attention tracker. Core research does not place trades or give price targets, and exported fields do not change that.

When is dashboard Plus enough?

Dashboard Plus is enough whenever a person looks at the board, makes a judgment, and writes the result down. That covers most solo researchers and many small desks. Plus is $200/mo or $2,000/yr and includes live ranks, whales, trackers, alerts, member chat, and 90-day pick history. New accounts start with a 14-day Plus trial, and the Breakflare Trading agent is included in paper mode by default.

The practical test is simple. If your weekly output is a short list of names and a sentence per name, the terminal already does the job. The daily rank 51-500 watchlist workflow is built around exactly that: sort by Breakout Index™, read confidence, star a handful, and revisit on a schedule. Nothing about it requires a file.

Plus is also enough when the “export” is really a note. Plenty of desks copy the day’s finalists into a shared sheet, a chat thread, or a research log. That is a manual export, and it is a perfectly respectable one. It forces a human to look at each row, which is the habit the shortlist size limit is trying to protect. A copy-paste routine that takes four minutes and produces a reviewed list beats an automated feed that nobody reads.

The mistake worth avoiding is asking for programmatic access to fix a discipline problem. If the board is opened on random afternoons, if stars pile up past ten, or if confidence is skipped when a chart looks exciting, a feed will deliver the same mess faster. Build the habit first. A clean first week on the Plus trial tells you more about your readiness than any integration plan.

When are datasets or the API the right next step?

Datasets or the API become the right next step when the dashboard is no longer the bottleneck and the constraint is where the numbers need to live. In other words, the desk has a real downstream consumer and a person who will maintain it.

Public docs describe two shapes. The Data API is REST access to the same daily scores behind the terminal: hype, Climb, Breakout Index™, confidence, catalyst labels, and thin market context for one UTC snapshot per day. Datasets are Parquet and CSV files of the same proprietary columns, aimed at models, research notebooks, and backtests. Both are scoped to the mid-cap band, not the whole market.

Which one fits depends on how the fields will be used:

A few signals suggest you are ready. Your team keeps a locked record of what the board said each day, in the spirit of reading 90 days of pick history. You have named the system that will read the fields, and someone owns it when a column changes. And you treat attention scores as research inputs, not as something to wire to orders without your own written gates.

It also helps to separate the two clocks. The terminal has a live board during the session, while the history you quote later comes from the daily lock. That difference is covered in live board vs UTC lock, and it matters even more once files are involved. A file that mixes a live read with a locked read is the same unlabeled-screenshot problem in a spreadsheet. Decide which clock your export follows and name it in a column header.

How do you prepare a clean shortlist export first?

Prepare the export by deciding what a row means before any system reads it. This is the part most requests skip, and it is the part that decides whether the data gets used.

Start with one UTC day. The UTC snapshot habit exists so that every coin in the band is compared on the same research day. Your export should carry that date on every row, because a file without a date is a rumor.

Then decide the minimum fields. For most desks this is a short list: coin identifier, snapshot date, rank, hype, 3d and 7d momentum, Climb, Breakout Index™, and confidence. Confidence deserves its own column rather than a footnote. A row with thin coverage should be easy to filter out, which is the same instinct behind confidence-first reading on the board.

Add your own columns next to the Breakflare ones, not inside them. Reviewer initials, a hold or fade tag, and a one-line reason keep the human judgment visible. Those columns are what let you ask later why a name stayed.

Finally, write the review cadence into your process doc. Daily, weekly, or event-driven are all fine. The weekly mid-cap attention review is a good model: one fixed slot, a short list of stars, and a decision per name. A feed with no scheduled reader turns into noise.

How does request access work without overselling it?

Request access works as a manual review, and it is worth describing that plainly. You open the request-access page in the docs, fill out the form, and the team reads your use case before anything is enabled. Request Data API access is the entry point for the API, Datasets, or both.

The form asks for a work email, a company or project name, an optional website, which product you need, an optional expected volume bucket, and a free-text use case. Approval is not automatic, and the docs say replies typically take a few business days. After approval, onboarding steps and private commercial terms follow. Rates are not published on the site, so this post does not quote any.

Three points keep expectations honest:

1. It is not included with Plus. The docs state that keys are not included with dashboard plans. The Data API is a separate commercial product, so approval for one does not change the other.
2. It is not an upgrade button. Requesting access does not move your account up a tier or unlock extra rows on the board. It opens a conversation about delivery.
3. It is not a promise of coverage you have not seen. The data is the same mid-cap band the terminal tracks, with the same scoring stack explained in the Breakflare scoring stack. Files and keys do not add a different hype definition.

Datasets also come with a license. The public summary says files are for internal research, models, and products, and that redistributing or reselling the raw files is not allowed. If your plan involves passing data to clients, say so in the form instead of hoping nobody asks.

If your needs are bigger than a data product, such as SSO, SLAs, or negotiated redistribution terms, that is a different conversation. The comparison in Plus vs Enterprise walks through when a desk crosses that line. For most teams, the honest order is Plus habit first, then data access, then anything larger.

What should a good use-case description say?

A good use-case description is specific about the consumer, the cadence, and the guardrails. Requests that are easy to evaluate share a shape.

Name the system. “An internal research portal that shows the daily Breakflare cohort beside our own notes” is clear. “Data for AI” is not. Name the cadence: once per UTC day, weekly, or a single historical study. Say whether you need the API, Datasets, or both, and give a rough volume bucket if you know it.

Then state the guardrails in a sentence or two. Examples: fields are used for internal research only, nothing is redistributed, and no order is placed from a raw score. If you plan to connect to the Breakflare Trading agent or any execution tool, remember that live use runs on your own exchange keys and credits, and the paper-first path is still the sensible rehearsal. A data pull is not a reason to skip it.

Mention your Plus history if you have it. A sentence like “we have used the live board daily since our trial and review stars every Friday” gives context without any attachment.

How do you keep a research-only boundary once data leaves the terminal?

Keep the boundary by treating every exported field as an attention measurement, not a forecast. Breakflare ranks hype, momentum, Climb, Breakout Index™, and confidence for CoinGecko ranks 51-500. It does not publish price targets, and core research does not place trades. A column named Breakout Index™ in your warehouse is still a research input.

A few habits help the boundary survive handoffs between people:

• Label the source and the clock. Put the snapshot date and whether the read was live or locked on every table. Later readers will assume otherwise.
• Keep confidence beside score. If a dashboard cell shows Breakout Index™ without confidence, someone will over-trust it. The pairing is in the confidence score guide.
• Do not rewrite history. If you correct a mistake, add a new row or a note rather than editing the old one, so the record keeps its audit value.
• Separate research from execution. Anything that places orders should read written gates you approved, not a raw score on its own.

These habits cost little and they protect the one thing that makes a data feed worth paying for: you can still explain, months later, why a name appeared on your list.

What is a sensible order of operations?

Run the board, write the process, then ask for access. Spend a few weeks on the same UTC sort, keep a simple log of stars and outcomes, and hold a weekly review. When you notice you are copying the same fields into the same place every day, you have found a real integration need, and you can describe it in the form without guessing.

Want the live rank 51-500 board, whales, alerts, and paper Trading agent first? Start a 14-day Plus trial at app.breakflare.com, and revisit the request form once your daily loop is proven.

Frequently asked questions

Is the Data API included with Plus? No. Plus is the dashboard plan with live ranks, whales, trackers, alerts, member chat, and 90-day pick history. The Data API is a separate product reviewed by request, and the docs state that keys are not included with dashboard plans.

What does request access review? The form collects your work email, company or project, optional website, whether you want the API, Datasets, or both, an optional volume bucket, and a use case. The team reviews the use case manually before enabling keys or arranging downloads. Replies typically take a few business days, and rates are shared privately after approval.

Can I export locked top-10 history? Plus lets you read 90 days of pick history in the product, and the locked top-10 is a published scoreboard for accountability. A file of that cohort is not something Plus promises. If you need locked history in a file for backtests, say so in your Datasets request and confirm the exact scope in the reply.

Should a solo researcher request the Data API? Usually not yet. If one person reads the board and writes a short list, Plus does the job. Ask once you can name a system that will consume the fields and a schedule for reading them.

Do exported scores come with price targets? No. Breakflare tracks attention across CoinGecko ranks 51-500. Core research does not place trades or give price targets, and data delivery does not change that.

Related reading

• Breakflare Scoring Stack: Hype, Momentum, Climb, Breakout Index™, Confidence
• Daily Rank 51-500 Watchlist Workflow for Crypto Attention Research
• Plus vs Enterprise: when a desk outgrows the terminal
• How to read 90 days of locked pick history