Every consequential thing your organization does travels as language. The pitch, the memo, the testimony, the apology, the ad. You can measure your revenue to the penny and your latency to the millisecond, but the words themselves, the actual instrument of change, have been scored by exactly one method for three thousand years: somebody's gut. Pulp ends that.
The Pulp API is the programmable interface to the P.U.L.P. framework, the Parametrically Unified Language Protocol: a system for reading, scoring, simulating, and shipping persuasive communication. Four packages, one question each.
Each package answers a single question. Learn the four questions and the whole platform becomes legible.
Radiance
What does this message say, why does it work, what does it stand on?
Windfall
What will happen when real people meet this message?
Groundwater
Who keeps all of this running?
loosethreads
Where does the conversation actually happen?
Everything in Pulp scores against the same eight dimensions of persuasive force. Scores run 0 to 100 on each dimension and combine into a single persuasive force reading, but the dimensions are where the diagnosis lives. A message that fails is almost never weak everywhere. It is weak somewhere specific, and specific is fixable.
| Dimension | What it measures |
|---|---|
| Ethos | The credibility the message earns or borrows |
| Pathos | The emotional charge it carries |
| Logos | The logical structure and evidentiary weight |
| Kairos | The fit between message and moment |
| Style | The craft of the language itself |
| Clarity | How little work the reader must do to understand |
| Focus | How completely the message serves a single intent |
| Awareness | How well it anticipates its actual audience |
Pulp is designed like the ecosystem its names come from.
The dependency story is deliberately simple. Radiance, Windfall, and Groundwater depend on nothing. loosethreads depends on all of them, because a conversation kit that cannot reach the engines is a coloring book.
One definition is load-bearing for everything else: content is anything that creates conversation. And a conversation is a turn-based exchange of payloads between two or more actors and agents, where every payload travels on a contract: the agreed terms of the exchange. Who may speak, in what scope, within which limits, under whose moderation. When you configure a thread, you are not setting widget options. You are writing a contract, and every turn that follows is performed on it.
The notation is small enough to hold in your head. Actors are people: A, B. Agents are software acting for a person: A′ is A's agent. Turn zero, A sends payload P to B, on contract. Turn one, B answers. That is the whole primitive, and the entire platform is operations on it. Radiance scores a turn. Windfall rehearses the other side's next turn before you commit to yours. Groundwater carries turns. loosethreads is where turns happen.
Two consequences are worth saying out loud. First, a document is not a finished thing. It is turn zero, waiting: a product page is an opening move and the review is the reply. Second, there is a conversation before the conversation: A and A′, you and your agent, arguing about the message before B ever sees it. We call it the metacognitive conversation, and it is the highest-leverage exchange in the graph, because it is the only one where revision is free. Thinkwell™ exists to make that conversation rigorous.
The Getting started guide walks from an API key to your first persuasion score in about a minute. When you are ready to go deeper, the Server-Side SDK documents the engines in full, and the Web SDK covers the React side.
Next: Getting started