agents.writerslogic.com
Sentiment analysis and a calibrated 0-100 probability that a Polymarket/Kalshi-style event resolves Yes.
- Category
- Data & research
- Starting price
- $0.005
- Paid calls · 30 days
- 0
- Unique payers · 30 days
- —
Paid endpoints
225 endpoints, sorted by usage. Prices are per request.
- POST/api/v1/pipelines/cra-readiness
Repository or manifests in, EU Cyber Resilience Act Art. 14 position out: dependency-advisor resolves every declared package to its locked version (deterministic, no model), those versions go to cra-exploit-clock as package URLs (OSV, CISA KEV, EPSS, EUVD), and each actively exploited component is joined back to the manifest that declares it with the fixed versions and the advisor's findings. Repo
$2.40Base0calls / 30d - POST/api/v1/pipelines/citation-audit
Bibliography in, evidence audit out: reference-verifier checks every reference (fabricated, mis-cited, retracted, corrected); the top DOI-bearing references (corrections first, then the most cited in the manuscript) get a replication-auditor pass on the sentence that cites them; when a target is contested, paper-contradictions compares it with the studies against it. The contradiction check is opt
$3.20Base0calls / 30d - POST/api/v1/pipelines/token-vault-ladder
One decision on holding a Base token and a vault position: token-trap-detector (live bytecode, proxy slots, honeypot simulation) and vault-exit-lawyer (redeem limits, queue, admin powers, eth_call simulation) run in parallel; contract-auditor then audits the token's verified source at the proxy implementation the trap step read, and is skipped on a honeypot or unverified source. Returns the worst
$1.20Base0calls / 30d - POST/api/v1/mesh-check
Checks a binary or ASCII STL mesh of up to 4000 triangles for a 3D-printing or CAD agent: open (boundary) edges, edges shared by more than two triangles, inconsistent winding, degenerate and duplicate triangles, normals that disagree with the vertex order, and an inside-out (negative signed volume) closed mesh, with triangle indices as witnesses. Input is base64 of the STL file (up to 200084 bytes
$0.005Base0calls / 30d - POST/api/v1/http-outcome
Classifies one HTTP response (method, status, headers) as success / retry / reconcile / stop for an agent that just called an API, and reads the wait from Retry-After (RFC 9110: delay-seconds or any of the three HTTP-date formats) or from a vendor delay header whose dialect the caller declares (seconds, milliseconds, epoch seconds, epoch milliseconds, HTTP-date). Caller-supplied vendor rules (stat
$0.005Base0calls / 30d - POST/api/v1/patch-anchor
Applies unified-diff hunks (wrong line numbers are fine) or search/replace blocks to a supplied file text and returns the patched text, for an agent whose edit tool failed or whose diff has drifted line numbers. Each hunk is located by its content against the original file, trying exact, trailing-whitespace, outer-whitespace then collapsed-whitespace matching; the rung used is reported per hunk. I
$0.005Base0calls / 30d - POST/api/v1/edit-anchor-check
Counts how many times an old-string occurs in a supplied file text (as a replace-in-file tool would see it) and returns each match's offset, line, column and surrounding lines, for an agent about to issue an edit. pass: exactly one literal match, even counting overlapping ones. unknown: several matches, or one match that overlaps another occurrence of the same text (ambiguous; contexts show how to
$0.005Base0calls / 30d - POST/api/v1/retry-admissibility
Given a request's method, how it ended (response status, timeout, reset, refused), idempotency-key evidence and optional caller policy, returns retry / do-not-retry / reconcile / unknown for an agent deciding what to do after a failed tool or API call. Encodes RFC 9110 method idempotency, the proxy and retry-of-a-retry rules and Retry-After parsing; a timeout or reset is never read as success or a
$0.005Base0calls / 30d - POST/api/v1/mutation-intent
Compares the JSON document an agent read (before) with the one it is about to write (after) and lists every change by JSON Pointer: removed members, null turned into omitted (and the reverse), arrays emptied or shrunk, objects emptied, type changes. Fails when a change touches a protected path or is destructive and not listed in allowDestructive; use it before a PUT, PATCH or bulk update. Arrays a
$0.005Base0calls / 30d - POST/api/v1/idempotency-fingerprint
Hashes the fields you declare as the identity of an operation (JSON Pointers into each request) with RFC 8785 canonical JSON and SHA-256, so retries of the same operation get the same fingerprint regardless of key order, and flags the ways that breaks: an identity field missing, an identity field also declared volatile, identity values that look like timestamps, epoch times or UUIDs (heuristic), a
$0.005Base0calls / 30d - POST/api/v1/pagination-loop
Takes the pages an agent has fetched so far (cursor used, next cursor returned, item ids) and finds the failures that make a scan loop or lie: a next cursor already used, a page whose items were all seen before, a page that returned nothing new yet offers another cursor, a scan that has not ended. Optionally takes declared ordering and cursor assumptions and lists the omission risks they imply (of
$0.005Base0calls / 30d - POST/api/v1/workflow-transition
Given a caller-supplied state machine (transitions with optional event names and required facts), the current state and a requested event or target state, says whether the transition is allowed, which required facts are false or unknown, and which transitions are available from the current state. For an agent about to move an order, ticket, deployment or approval to its next state. Terminal states
$0.005Base0calls / 30d - POST/api/v1/deadline-feasibility
Takes steps with expected and worst-case durations, dependencies (steps with no dependency between them run in parallel), retries with backoff, and the time remaining, and computes the critical path for both cases. Verdict guaranteed (worst case fits: pass), likely (only the expected case fits: unknown) or infeasible (even the expected case does not fit: fail), with the slack and the critical-path
$0.005Base0calls / 30d - POST/api/v1/update-dialect
For an agent about to send a PATCH or update body: states, per field, what omitted / null / [] / "" mean under the declared dialect (RFC 7396 merge patch, RFC 6902 JSON Patch, or caller-declared semantics) and checks the body against stated intents such as 'clear this field', 'leave this alone' or 'set to empty array'. With a target document it applies the patch and compares the result; without on
$0.005Base0calls / 30d - POST/api/v1/compensation-coverage
For an agent plan made of steps with declared effects (read or write), checks every write in the plan, run or not, has a compensation step that exists, is itself a write, is not its own compensation, and that the dependencies have no cycle; flags writes declared irreversible; and, given which steps have completed, returns the compensations to run in reverse completion order. Does not judge whether
$0.005Base0calls / 30d - POST/api/v1/approval-invalidation
Compares what a human or system approved with what is about to be executed (a quote, order, plan, diff summary: any JSON) under a caller-supplied materiality policy: per-path rules exact / ignore / numeric tolerance (absolute or percent) / no-increase / no-decrease, with the longest matching path winning and a default for unlisted paths. Also covers quote revisions (approved revision number must e
$0.005Base0calls / 30d - POST/api/v1/quota-reservation-check
Computes available quota from a caller-supplied snapshot (limit, used, reserved) minus the unexpired pending reservations and says whether a requested amount fits. This is a read of the numbers you supply as of snapshotAt: it reserves nothing, so concurrent consumers can still use the quota before you do, and every response says so. A stale snapshot gives unknown, not pass; a window that ended at
$0.005Base0calls / 30d - POST/api/v1/transcript-validator
Validates a message list before it is sent to Anthropic Messages, OpenAI Chat Completions or OpenAI Responses: every tool call paired with its result, results in the right place and role, ids present and unique. Built for an agent that edits, truncates or replays its own history and would otherwise get a 400. Only rules stated in the providers' documentation fail the check; anything else suspiciou
$0.005Base0calls / 30d - POST/api/v1/dedup-window
Given previously seen deliveries (identity, receivedAt, payload or digest, handling outcome) and a new incoming one, finds earlier deliveries with the same identity inside the window and returns process (none), dedupe (same payload already processed), retry (earlier ones all failed), reconcile (an earlier one is in flight or unknown, or the same identity arrives with a different payload) or abstai
$0.005Base0calls / 30d - POST/api/v1/cache-key-check
Given the inputs of a cached computation (each declared as influencing the output or not, optionally volatile) and the list of inputs the cache key is built from, finds influential inputs missing from the key (stale or wrong hits), volatile inputs inside it (the cache never hits), unknown-influence inputs left out, and, for private results, a missing tenant dimension (cross-tenant leak). When valu
$0.005Base0calls / 30d - POST/api/v1/delegation-contract-check
Checks the brief an agent is about to hand to another agent: the required parts are present and non-empty (objective, acceptance criteria, a budget with at least one positive numeric bound, required evidence, stop conditions; output format if required), nothing is duplicated, and acceptance criteria are not made only of vague wording (a small labelled word list: good, appropriate, if possible ...)
$0.005Base0calls / 30d - POST/api/v1/artifact-invalidator
Given a dependency graph of artifacts (each lists the artifact ids it was derived from) and the ids that changed, returns every artifact that transitively depends on a change, in an order safe to recompute (inputs before dependents), and the artifacts that are unaffected. A cycle or an unknown input id is a defect in the graph and returns fail with the cycle path. Changed ids that are unknown fail
$0.005Base0calls / 30d - POST/api/v1/permission-intersection
Computes what a sub-agent may actually do: the permissions it requested, intersected with what the end user holds and what its parent agent holds, minus any explicit deny list, and says for each denied permission which party lacks it. Permission names are compared exactly (no wildcards); caller-declared implications (for example 'admin' grants 'read') can be given and are expanded transitively wit
$0.005Base0calls / 30d - POST/api/v1/assumption-conflict
Takes assumptions that several agents or steps hold about the same fact (key, value, who) and reports every key where the values differ, naming the conflicting pairs and whether they differ only by case or whitespace (a formatting difference) or in substance (USD vs EUR, a different id, a different version). Optionally requires each listed agent to state each required key; a missing statement is u
$0.005Base0calls / 30d - POST/api/v1/test-exit-interpret
Reads a finished test run (runner, exit code, optional version, flags, caller-parsed counts, optional go test output, optional per-attempt exit codes) and says whether tests actually passed, ran nothing, were all skipped, passed only on retry, or never ran properly (timeout, signal, internal error). Encodes only exit-code semantics the runners document: pytest 0-5, node:test, mocha (failure count
$0.005Base0calls / 30d - POST/api/v1/duplicate-key-audit
Scans raw JSON text (RFC 8259) for repeated object member names at any depth, including inside arrays and keys spelled differently but equal after unescaping ("a" vs "\u0061"), and reports each with its JSON pointer, UTF-8 byte offset, line, column and the value every occurrence carried, plus whether the values conflict. Also reports a leading BOM, unpaired surrogates, __proto__ keys and the exact
$0.005Base0calls / 30d - POST/api/v1/union-branch
Evaluates a JSON value against every branch of a oneOf or anyOf in a caller-supplied JSON Schema 2020-12 (or OpenAPI schema converted to it) and reports which branches match, the exact errors of each branch that fails with the JSON pointer of each offending value, the closest branch, and which branch an OpenAPI `discriminator` points to. For agents debugging why a tool or API payload is rejected w
$0.005Base0calls / 30d - POST/api/v1/lossy-conversion
Takes raw JSON literals (as written, so 9007199254740993, 1e400, -0, "007" and 0.10 are judged on their digits, not on a parsed double) and target types (binary64, binary32, int8..int64, uint8..uint64, PostgreSQL numeric(p,s), Arrow decimal128/decimal256, Parquet decimal, Excel cell, pandas int64) and reports for each pair whether the value is exact, lossy (rounded, truncated, leading zeros or sig
$0.005Base0calls / 30d - POST/api/v1/cross-field-rules
Evaluates up to 100 rules you declare over one JSON document and reports, per rule, pass, fail or unknown with the JSON pointer of every violating field and the actual value class (absent, null, empty string, value). Rule kinds: compare (>, >=, <, <=, ==, != on numbers, exact decimals, RFC 3339 dates or date-times, strings), required-if, forbidden-if, exactly-one, at-most-one, at-least-one, all-or
$0.005Base0calls / 30d - POST/api/v1/json-patch-conflict
Takes one base document and 2 to 4 JSON Patch (RFC 6902) operation lists written against it and reports, per pair, whether they commute: same-path writes, ancestor/descendant overlaps, array-index shifts (an insert or remove moves the elements a later patch addressed by index), concurrent `-` appends whose final order depends on application order, `test` operations invalidated by another patch, an
$0.005Base0calls / 30d - POST/api/v1/schema-repair
Validates a JSON value against a caller-supplied JSON Schema 2020-12 and applies only the coercions you list (for example string-to-integer for "42", trim-strings, enum-case, apply-defaults, drop-additional) when each one strictly reduces the number of schema errors. Every change is returned with its JSON pointer, the rule, the old and new value; every error that remains is returned with its exact
$0.005Base0calls / 30d - POST/api/v1/schema-witness
Walks a caller-supplied JSON Schema 2020-12 and, for every constraint keyword (type, enum, const, minimum, maximum, exclusiveMinimum, exclusiveMaximum, multipleOf, minLength, maxLength, pattern, format, minItems, maxItems, uniqueItems, required, minProperties, maxProperties, additionalProperties false, dependentRequired), returns the JSON pointer of the constraint, an example that satisfies it and
$0.005Base0calls / 30d - POST/api/v1/csv-roundtrip
Parses CSV text (RFC 4180, caller dialect) against a column type map and reports, per cell with row, column, physical line and byte offset, everything that would change on a parse-serialize-parse round trip or when opened in Excel or Sheets: leading zeros stripped, integers beyond 2^53 or 15 significant digits, scientific-notation and date coercion ("1E5", "1-2", "MARCH1"), formula injection (= +
$0.005Base0calls / 30d - POST/api/v1/csv-dialect
Detects the delimiter (comma, semicolon, tab, pipe), quote character, line terminator, BOM, header row offset (preamble lines above the header) and whether a header exists in CSV text, parsed per RFC 4180 so quoted delimiters and CRLF inside quoted fields are handled. Returns every candidate dialect with its score, each ragged row with its physical line, and header repairs (empty, duplicate or BOM
$0.005Base0calls / 30d - POST/api/v1/openapi-slice
Extracts one operation (path plus HTTP method, matching templated paths like /pets/{id}) from an OpenAPI 3.0.x or 3.1.x document, given as JSON, YAML or a parsed object, and returns a smaller valid OpenAPI document holding that operation, its path-level parameters and servers, and the transitive closure of every local $ref it uses: schemas, parameters, requestBodies, responses, headers, examples,
$0.005Base0calls / 30d - POST/api/v1/enum-canonicalize
Maps each input string onto one member of a closed caller-supplied set using, in order: exact match, caller aliases, a deterministic normal form (Unicode NFKC, case and accent folding, punctuation and underscore collapse), then bounded edit distance (optimal string alignment, so a swapped pair of letters costs 1). Returns the canonical value, the method, the distance and the nearest candidates; it
$0.005Base0calls / 30d - POST/api/v1/schema-compat
Compares an old and a new JSON Schema 2020-12 (or two OpenAPI 3.0/3.1 documents) and lists each change with its path, keyword, old and new value, whether it narrows or widens what is accepted, and whether it breaks clients: newly required properties, removed or retyped properties, removed enum values, tightened limits, additionalProperties flips, removed operations, removed or newly required param
$0.005Base0calls / 30d - POST/api/v1/sentinel-values
Scans columns of values for sentinels. Values you declare in a dictionary (for example -1 means unknown in column age) are reported as asserted hits with their row paths. Other values that look like missing-data markers are reported separately as candidates, never asserted: the pandas default NA strings, spreadsheet error values, whitespace-only text, placeholder words, zero and epoch dates, fixed
$0.005Base0calls / 30d - POST/api/v1/metric-comparability
Compares two structured metric definitions field by field (numerator, denominator, aggregation, weighting, population, filters, exclusions, period grain and calendar, timezone, currency, FX and tax basis, unit) and returns which differences make the numbers not comparable, which are adjustable with raw data, and which fields are missing from one side. In drift mode a is the old and b the new defin
$0.005Base0calls / 30d - POST/api/v1/join-cardinality
Takes the join keys of two tables (every row's key, or distinct keys with row counts) and computes the exact output row count of an inner, left, right or full equi-join with SQL NULL semantics, the observed cardinality (one-to-one, one-to-many, many-to-one, many-to-many), the keys that multiply rows the most, unmatched keys on each side and the first duplicate row when a side was assumed unique. I
$0.005Base0calls / 30d - POST/api/v1/citation-span
Finds each quote an agent attributes to a source text and returns where it sits: exact offsets in UTF-16, code points, UTF-8 bytes and graphemes, so the span slices back to the matched text. Tries an exact match, then a match tolerant of whitespace, curly vs straight quotes, dash types, ellipses, invisible characters and Unicode forms (NFC/NFD, ligatures), naming which normalizations were needed,
$0.005Base0calls / 30d - POST/api/v1/config-migration
Applies a declared mapping (from pointer, to pointer, optional transform such as string-to-number or a value map) to a v1 JSON config, carries over unmapped keys the v2 schema declares, fills schema defaults, validates the result against the v2 JSON Schema 2020-12 and returns the migrated config plus three exact lists: dropped (v1 values that landed nowhere, with their JSON pointers), defaulted (v
$0.005Base0calls / 30d - POST/api/v1/constraint-carryover
Takes the constraints an agent was given (budget caps, deadlines, identifiers, prohibitions) and a later artifact (plan, summary, handoff, tool arguments) and reports for each constraint whether its concrete atoms still appear: numbers with their unit or currency, ISO dates, codes, quoted terms, or caller-listed anchor strings, with offsets. For a negated constraint it also reports whether the clo
$0.005Base0calls / 30d - POST/api/v1/context-pack
Chooses which context items an agent should put into a prompt without exceeding a token budget: every mandatory item and everything it depends on is always included, then optional items by descending priority (each with the dependencies it pulls in) while they fit. Token counts come from the caller or from o200k_base / cl100k_base; any other tokenizer name returns unsupported (there is no Claude t
$0.005Base0calls / 30d - POST/api/v1/syndication-hint
Compares up to 30 passages an agent collected and reports which pairs share word-shingle content (Jaccard and containment), grouping them into clusters of probable copies so the number of independent sources can be stated honestly. Does not establish who copied whom, does not detect paraphrase or translation, and does not fetch anything; a high similarity is a hint that sources are not independent
$0.005Base0calls / 30d - POST/api/v1/evidence-bundle-check
Checks a bundle an agent assembled before answering: each claim must be backed by at least N evidence items from distinct source groups, each item's quote must actually appear in the supplied text (with offsets), publication dates must be within the caller's maximum age relative to a caller-supplied asOf, and duplicates are collapsed. Does not fetch URLs or judge whether a source is reliable or wh
$0.005Base0calls / 30d - POST/api/v1/hedge-extract
Finds hedge and booster cues in an agent's or source's text using a fixed English lexicon (modals, epistemic verbs, adverbs and adjectives, approximators, shield phrases, certainty boosters) plus caller-supplied phrases, and returns each cue with its category, the sentence it sits in, and offsets in UTF-16, code points, UTF-8 bytes and graphemes. Rule-based and English only: a cue is a word match,
$0.005Base0calls / 30d - POST/api/v1/negation-scope
Applies NegEx-style rules (the English termset of negspacy, MIT, derived from NegEx) to text: finds negation cues, pseudo-negations such as 'not only', and scope terminators such as 'but', and returns each cue's scope window with offsets in UTF-16, code points, UTF-8 bytes and graphemes. Given target terms, reports per occurrence whether it is negated, not negated by the rules, or unknown (near a
$0.005Base0calls / 30d - POST/api/v1/log-collapse
Groups the records of a log or CI output by signature: timestamps, UUIDs, IPs, hex ids, quoted values and numbers are replaced by placeholders, stack-trace continuation lines are attached to their record and contribute their first frames, and each signature reports its count, severity, first and last line, first and last timestamp (as written, when the line starts with an ISO 8601 timestamp) and a
$0.005Base0calls / 30d - POST/api/v1/deictic-check
Scans a user or tool message for phrases that cannot be understood without context: demonstratives ('that one', 'the latter'), back-references ('as before', 'the usual'), and relative dates or times ('tomorrow', 'next Friday', 'end of month', 'soon'), each with offsets and a clarification question. Given a caller anchor (asOf instant plus IANA time zone) it resolves only unambiguous day offsets (t
$0.005Base0calls / 30d