01 / DEFINE
Start with
the question.
Describe what a reader needs to know or what a participant is being asked to decide. The interface and vocabulary should follow that purpose.
ABOUT VOTEAPI.COM
More context.
Better questions.
VoteAPI.com is a practical reference for understanding the many ideas behind a vote API: information, uncertainty, participation, platforms, and governance.
OUR FOCUS
Make the meaning
easier to find.
The same vocabulary appears in election reporting, informal polls, probability feeds, nonprofit decisions, and blockchain governance. Each setting has different rules and a different relationship between a record and the real-world process behind it.
Our guides help readers identify those differences. They connect the purpose of an integration to the data it needs, the authority behind it, and the experience of the person using it. Developers can use them to frame a data contract; editors and organizers can use them to ask clearer questions.
The website serves a global audience. When an article uses a jurisdiction-specific example, it names that scope. Official election rules and personal voting records should always be checked with the responsible election authority.
Start with
02 / TRACE
Keep the
source visible.
Carry origin, scope, timing, and status with the information. A polished presentation should make its interpretation easier to examine.
03 / EXPLAIN
Show the
important limits.
Separate an illustrative data model from an available service, a probability from a result, and an identity claim from a participation decision.