Dev.to AI 🤖 Ai 👁 0 📖 3 min read

Build a Crypto News Agent with Bluwhale Bluprint

A useful news brief should make it easy to go from a short summary to the original announcement. In this guide, we'll build a BTC and ETH news agent using Bluwhale Bluprint. The goal is straightforward: up to five relev

Build a Crypto News Agent with Bluwhale Bluprint

A useful news brief should make it easy to go from a short summary to the original announcement.

In this guide, we'll build a BTC and ETH news agent using Bluwhale Bluprint. The goal is straightforward: up to five relevant updates, each with a headline, a short summary, a publication date and a direct source link.

You'll configure the agent through the interface and request a brief from its chat. No code is needed for this version. The prompts also give you a structure you can adapt to other topics, such as library releases or security advisories.

1. Choose the news template

Sign in and open Bluprint, then select Create Agent → Research → Daily News Brief.

If the builder opens on Trading, switch to Research first. The news template provides a starting request about BTC and ETH, then asks what the brief should focus on.

Research selected in Bluprint Agent Builder, with the Daily News Brief template

2. Define what belongs in the brief

"Keep me updated on crypto" leaves a lot of decisions to the agent. Give it a topic, a time window, preferred sources and an output format.

Paste this into the customization field:

Create a read-only BTC and ETH news brief focused on protocol/technical updates and
regulatory announcements from the last 24 hours. Prefer official primary sources. Return
up to 5 bullets, each with a headline, a 1-2 sentence summary, the source URL and
publication date. Include the time of the brief in UTC. If a source or date cannot be
verified, say so rather than inventing it. Do not place trades or connect to a wallet.
Name: BTC ETH News Brief - Tutorial.

A few choices make this prompt reusable:

  • Specific topics give the agent a clear basis for selecting news.
  • Primary sources point the brief toward original announcements.
  • Up to five items allows a shorter answer when there is less relevant material.
  • A consistent format makes each update easy to scan and follow up.

Review the builder's summary, then select Looks good, create it!

Bluprint summarizing the BTC and ETH news agent specification before creation

3. Ask for your first brief

The agent opens in Testing Mode. Send this message to request a brief:

Run one BTC and ETH news brief now for the last 24 hours. Focus on protocol/technical
updates and regulatory announcements. Include up to 5 items with headline, a 1-2
sentence summary, direct source URL and publication date, plus the brief time in UTC.
Use official primary sources. If no qualifying update can be verified, say so.

Here is the response from the October 17 walkthrough:

BTC and ETH news brief showing an Ethereum update, its source URL, publication date and UTC brief time

The agent returned one item about Ethereum's Glamsterdam upgrade on the Hoodi testnet. It included a short explanation, the publication date and a link to the Ethereum Foundation announcement.

That gives you a compact reading list: scan the summary, then open the original source for the details.

4. Follow the source

The linked Ethereum Foundation announcement confirmed the Hoodi activation schedule and that the mainnet date was still undecided. The summary preserved that distinction.

This is where the source link earns its place in the output. A testnet announcement and a mainnet launch have different implications, even when they concern the same upgrade.

There was also a useful detail for refining the prompt: the announcement showed a publication date but no exact publication time. For a strict rolling 24-hour cutoff, ask for publication timestamps and have the agent flag items whose timing cannot be established.

Make it fit your workflow

This version runs on demand from the agent chat. To adapt it, change the subject and source preferences while keeping the output format:

  • Library releases: version, main changes, release date and official release notes.
  • Security advisories: affected software, advisory date and the original advisory.
  • Protocol updates: network, upgrade status, relevant dates and the official announcement.

The starting point is a small, repeatable task with an output you can actually use. Scheduling and delivery can come later, once the brief covers the information you need.

For developers building similar agents: would you start with a fixed list of trusted sources, or let the agent discover sources for each brief? How do you balance coverage with keeping the results easy to review?

Author note: I work with Bluwhale on SEO and content. This walkthrough and article were prepared with AI assistance.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.