QuassLabs API status
Answered our latest tool-list check 5 hours ago with 37 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 06:16 UTC
- Last commit
- 13 Nov 2026
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 06:16 | Answered | 2.9 s | 37 |
| 16 Nov, 06:16 | Answered | 2.1 s | 37 |
Tools (37)
Read from the server on 17 Nov 2026.
- alignment_gate
- Run an AI system prompt (and optional agent config) through a 45-criterion alignment/safety rubric. Returns a letter grade (A-F), numeric score, per-flag remediation, and a pass/fail verdict.
- blm_land_lookup
- Look up Bureau of Land Management land status for a US coordinate: BLM ownership, jurisdiction, allowed activities (rockhounding, camping), permit requirements, and special designations (ACEC, Wilderness, WSA, NM/NCA).
- diagram_contrast
- Diagram quality QA. Catch and fix the things that ruin diagrams: (1) unreadable label contrast - POST a mermaid/SVG or HTML diagram, get every WCAG-AA failure (incl. mermaid <style>-block label colors, with unresolvable fills flagged honestly, not false-passed) + auto-corrected colors; (2) harden a mermaid SOURCE before it renders - rewrites every fill/label pair and remaps fills no label color ca
- humanizer_score
- Detect AI-writing tells in text. POST prose and get a 0-1 ai_ness score + band (low/medium/high) + the EXACT patterns that fired (AI vocabulary, significance inflation, promotional language, filler phrases, negative parallelism, rule-of-three, em-dash overuse) with sample spans. Explainable, not an opaque classifier - every point is a named, located pattern. Deterministic, no LLM. The rewrite is a
- saas_metrics
- SaaS health advisor. POST your MRR/customers (+ optional churn/CAC/margin/growth) and get ARR/ARPA/LTV/CAC/payback/Rule-of-40/NRR/GRR computed, each with a health tag, plus an overall grade + a ranked "what to fix first" focus list. Deterministic math + advisory, no LLM.
- acceptance_criteria_validator
- QA advisor: validate acceptance criteria quality. POST a list of AC (or a story) and get per-AC problems (vague/untestable, non-atomic, no observable outcome) + a missing-coverage flag if there is no failure-path AC, plus a 0-100 score and pass/needs_work verdict. Tells you exactly what to fix. Deterministic, no LLM.
- coverage_check
- Scope-completeness advisor. POST a brief (or requirements[]) + your stories[] and get a coverage score + the gaps (requirements no story covers), orphan stories (possible scope creep), and missing structural buckets (auth/CRUD/error-states/tests). Tells you what the scope is missing. Deterministic, no LLM.
- defect_triage
- Bug-triage advisor. POST one bug report (or a list) and get severity (critical/high/medium/low), category, whether it has repro steps, and what info is missing (no repro / no expected-vs-actual / no environment). For a list: priority ranking + likely-duplicate clusters. Deterministic, no LLM.
- model_advisor
- LLM selection + cost advisor. POST a task description (+ optional volume/tokens/constraints like local-only or cheap) and get a recommended model + fallback chain + do-not-use (with reasons), the complexity tier, and per-run + monthly cost. A maintained model+price catalog. Deterministic, no LLM. Tells the AI/user which model to use and what it costs.
- tool_advisor
- Which QL-API endpoint fits this task. POST a task description and get the ranked endpoint(s) that best match, each with a confidence label (high/medium/low). Deterministic keyword matching over this platform's own endpoint catalog, no LLM. Pairs with model_advisor (which itself is one of the recommendable endpoints, so a "which model" task surfaces it) - call them independently and chain the resul
- humanize_text
- Rewrite text to remove AI-writing tells. POST prose and get it back with the mechanical tells fixed (AI vocabulary swapped for plain words, filler phrases stripped, em-dash overuse reduced, significance inflation deflated) plus a change log, before/after ai-ness scores, and a residual list of tells that need human judgment (not auto-rewritten). Code fences, inline code, URLs, and quotes are never
- dependency_check
- Check dependency manifests. Price: free by default; with live: true, 2 credits up to 50 packages, +1 per further 50, max 5 (200 packages). Default: offline hygiene lint for unpinned, wildcard or unbounded versions, missing lockfiles, git/URL deps, non-https indexes, install scripts, dependency-confusion names, plus a static snapshot of famous compromised versions. live: true adds, per package, kno
- log_audit_creator
- Generate a concrete audit-logging spec for an app. POST your feature list (and optional compliance targets: soc2/hipaa/gdpr/pci) and get a full audit-event catalog (namespaced event names, actor/target/required fields, PII flags, retention), a canonical event envelope schema, a storage plan (append-only, access control, alerting), and per-framework compliance notes. A dev team can implement it dir
- log_analyzer
- Analyze a log file. POST raw log text (or an upload_id from the create_upload tool, up to 5MB) and get: level breakdown + time range, error clusters (messages normalized so variable ids/numbers collapse into one signature, with counts + first/last seen + a sample), a timeline, detected anomalies (error spikes, retry storms, new error signatures, log gaps/outages, level-ratio shifts) with evidence,
- ticket_lint
- Full Jira-ticket quality linter (whole ticket, not just AC - use acceptance_criteria_validator for the deep AC pass). POST one ticket or a batch (max 50) and get per-ticket findings with severity + concrete fixes: missing/weak summary or description, missing AC or estimate, bugs without repro/expected-vs-actual/environment, missing epic link, points-vs-hours mismatch, oversized estimates to split,
- story_lint
- Deterministic structural quality linter for user stories - a sibling to ticket_lint but scoped to story-writing concepts any team recognizes: narrative completeness (As-a/I-want-to/So-that/Summary), acceptance criteria presence, duplicate/unknown dependency IDs, a "Manage X" story with no CRUD split, list stories missing a pagination mention. An OPTIONAL rate_config unlocks team-specific checks (s
- estimate_sanity
- Deterministic classifier for story/task hour estimates against benchmarks: flags each estimate in_range, borderline, over, under, or unbenchmarked. Supply either an explicit {min, max} range per type (benchmarks) or a list of historical actual hours per type (historical) that this endpoint derives a mean/stdev variance band from - explicit ranges win when both are given for the same type. No bench
- pr_description_lint
- Deterministic PR description quality linter: flags a missing/too-short body, absent test evidence, absent stated rationale, an unstructured long body, and - only for PRs that look like bugfixes (title prefix fix/bug/hotfix/patch, or an explicit is_bugfix flag) - missing repro steps. Optionally requires a linked issue/ticket reference. Single PR only, no batch. Deterministic, no LLM.
- commit_hygiene
- Deterministic commit-message hygiene checker: conventional-commit format, vague-subject detection, subject-length limit, a same-message secret-pattern scan (AWS keys, private key headers, Slack/GitHub tokens, inline password=/secret= style credentials - checked against the message text only, never a diff), and an oversized-commit warning from caller-supplied insertions/deletions. POST one commit o
- readability_grade
- Deterministic Flesch Reading Ease and Flesch-Kincaid Grade Level for a block of text, plus word/sentence/syllable counts and a plain-language reading-ease band (very_easy through very_confusing). Syllable counting is the standard vowel-group heuristic (same approximation used by textstat and most open readability tools), not a dictionary lookup. Optionally pass target_grade to get an on_target fla
- regex_lint
- Static safety analysis of a regular expression plus an English explanation of what it matches. Parses the pattern into an AST and flags the structures that cause catastrophic backtracking (ReDoS): nested unbounded quantifiers like (a+)+, repeated alternations whose branches can start with the same character like (a|ab)*, adjacent unbounded quantifiers over overlapping character sets like \d+\d+, a
- mcp_tool_lint
- Static review of MCP tool definitions, as returned by a server's tools/list, for how well a model can choose and call them. Flags missing, too-short or vague descriptions; parameters with no description or type; free-form objects and arrays without items; required fields that are not declared; duplicate, case-colliding or near-identical tools; missing or contradictory annotations (readOnlyHint, de
- openapi_diff
- Compares a base and a head OpenAPI 3.x spec (JSON object, or a JSON or YAML string) from the API consumer's point of view and lists what would break existing clients: removed operations or 2xx responses, new required parameters or request properties, optional-to-required changes, narrowed request enums and tightened constraints, removed or now-optional response properties, widened response enums,
- actions_audit
- Static security audit of GitHub Actions workflow files. Flags template injection (attacker-controlled github.* contexts such as a PR title or branch name expanded inside run: or actions/github-script), pull_request_target and workflow_run triggers and the pwn-request pattern of checking out the pull request head under them, actions and reusable workflows not pinned to a full 40-character commit SH
- agent_card_lint
- Static lint of an A2A (Agent2Agent) Agent Card, the JSON an agent publishes at /.well-known/agent-card.json. Checks conformance with A2A v1.0.1 and the 0.3 field names (both dialects accepted): required fields present and typed, URLs absolute https (http allowed for localhost), input and output modes that look like MIME types, skills with id, name, description and tags, duplicate skill ids, and se
- data_transform
- Five deterministic data utilities behind one tool, chosen by operation. csv_normalize: sniffs the delimiter, strips the BOM and normalises line endings, snake_cases headers (duplicates renamed), pads or trims ragged rows, drops empty rows and optionally duplicate rows, and returns CSV or JSON rows (max 200,000 cells, 1,000 columns, 64 KB per cell). json_shape: infers a JSON Schema (draft 2020-12)
- skill_lint
- Static lint of an agent instruction file: an Agent Skills SKILL.md (YAML frontmatter plus markdown body) or an AGENTS.md / CLAUDE.md style file. For skills, checks the frontmatter against the Agent Skills specification: name present, lowercase-hyphenated, at most 64 characters and free of reserved words; description present, at most 1,024 characters, with no XML tags, written in the third person a
- sql_migration_lint
- Static lint of a SQL migration file (Postgres or MySQL) for operations that lock or rewrite live tables or break running application code. Flags CREATE INDEX without CONCURRENTLY and concurrent index builds inside a transaction, foreign key, CHECK and UNIQUE constraints added without NOT VALID or USING INDEX, SET NOT NULL without a validated CHECK, column type changes, NOT NULL columns added witho
- sprint_health
- Sprint/delivery health advisor. POST 1-24 sprints (committed/completed points, optional per-ticket estimate-vs-actual data) and get computed metrics each with a good/warn/bad health tag: velocity avg + trend + stability, commitment reliability, spillover rate, mid-sprint scope change, estimate accuracy (median + chronic-overrun pct), and WIP concentration per assignee. Plus an overall grade and a
- worklog_guardrail
- Worklog/timesheet policy checker - run a batch of worklog entries through configurable guardrails BEFORE posting them to a time-tracking system. Checks: rounding increment (default 0.25h, float-safe), per-entry min/max, per-author daily totals, duplicates, over-estimate alerts (never suggests inflating hours or estimates - flags to PM instead), future dates, weekends, immutable-author edit protect
- create_upload
- Get a presigned S3 PUT URL to upload a file (policy doc, config, log, up to 5MB) that a file-ingesting endpoint then reads by upload_id. Two-step: call this, PUT your file to the returned url, then pass upload_id to the consuming endpoint. Uploads auto-expire in 1 day and are readable only by your key. Auth required; not billed.
- send_feedback
- Submit free-text feedback about the API - a bug, an idea, a docs gap, a billing question, or anything else. Missing a tool? Use kind tool_request to tell us what you needed, with an optional tool_description. Tied to your key so we can follow up, but not a support-ticket SLA. Auth required; not billed.
- account
- Everything about your QuassLabs API account, chosen by `action`. Free: no action costs credits. "signup" (no API key needed): request a free key for an email address. A confirmation link is emailed; a human opens it on quasslabs.com to see the key, which is never returned to the agent. The key comes with 300 free credits a month. Always answers status check_email, whether or not the address alread
- rate_call
- Rate a specific prior metered call - thumbs up or down, plus an optional comment - keyed by the request_id that call's response reported. Works for any metered tool, so you can tell us when a result was wrong, unhelpful, or missed something. Resubmitting the same request_id overwrites your previous rating rather than adding a second one. Auth required; not billed - rating a call you already paid f
- supply_chain_scan
- Scan a whole repo archive (a ZIP of manifests, lockfiles and MCP server configs) for packages, MCP servers and extensions listed in a known-compromise catalog (Bumblebee threat intel). Use this for a repo, many lockfiles or MCP configs; use dependency_check instead to lint a few pasted manifests for pinning and hygiene. Send exactly one of archive_base64 or archive_url; neither or both is 400 exac
- describe_diagram
- Turn a plain-English description into Mermaid diagram source. Describe the flow, system, schema or timeline you want ("a login flow with an OAuth branch and a failure path") and get back complete, valid Mermaid - no need to know the syntax. The mermaid field of the response is directly usable as the mermaid_source input of convert_diagram, so describe -> render is a two-call pipeline. Generation r
- convert_diagram
- Make Mermaid diagrams portable. Takes HTML containing <div class="mermaid"> blocks (or a raw Mermaid source) and returns the same document with every diagram pre-rendered to inline SVG and the Mermaid CDN runtime stripped. A CDN-backed diagram only renders if the reader can fetch and run the runtime; inline SVG needs neither, so the output survives offline readers, email clients, Notion/Confluence