Read a thousand pages. Ask a model about every row. Send one request per record. Transform a whole column. Paste the list, pick the function, take the table.
BULKFORGE // ONE FUNCTION, EVERY ROW
A list goes in. The same operation runs down every row of it.
Pages read, prompts answered, requests sent, records reshaped.
12 ready-made batches · 5,000 rows a batch
01 / GETTING THE LIST IN
Drop a CSV, paste a spreadsheet column, or throw in a JSON export.
It finds the column, drops the blanks, and tells you what it dropped.
.csv · .tsv · .json · .txt · paste
02 / CHOOSING WHAT HAPPENS
Read a page, ask a model, send a request, build a query, resize an image.
Or chain them — step two reads step one, for that row.
03 / BEFORE YOU COMMIT
Preview resolves your template against the first few rows and shows the literal call.
One wrong token costs a glance instead of five thousand failures.
04 / THEN WALK AWAY
A queued batch survives a restart and resumes at the row it reached.
A failed row is a row — the run finishes and the table says which and why.
Send one HTTP request per item. The item can be interpolated into the URL, the headers or the body.
Fetch every URL in the list and pull its readable text out of the markup.
Title, description, canonical, Open Graph and Twitter cards, for every URL in the list.
Every outbound link on every page in the list — the fastest way to turn one list into a bigger one.
Run one prompt per item through a local model. This is the original BulkForge — a prompt template and a list of topics.
Two steps per item — fetch the page, then hand THAT page to a model. This is the shape a workflow loop gets wrong: here step 2 sees step 1’s output for the same item.