slop.how

A fast and free API for analyzing sloppy writing.

Paste this into your agent:

Use slop.how to review this text:

In today's fast-paced digital landscape, remote work isn't just a trend. It's a revolution. By leveraging cutting-edge collaboration tools, teams can unlock unprecedented productivity and foster a culture of innovation. The result? A seamless, empowered workforce. Let's dive in.

api.slop.how responds with:

  • canned_opening0.95

    Does the text open with a generic scene-setter about the era, the world, or the importance of the topic, e.g. "In today's fast-paced digital landscape", "In an era where", "X has become increasingly important"?

    Fix: Start with the specific point, fact, or example.

  • vague_claims0.94

    Does the text make general claims without concrete names, numbers, examples, quotes, or first-hand detail?

    Fix: Add a name, number, example, or first-hand detail.

  • buzzwords0.94

    Does the text lean on vocabulary common in AI-generated prose, such as delve, tapestry, leverage (as a verb), harness, unlock, seamless, robust, journey, landscape, elevate, realm, foster, crucial, pivotal?

    Fix: Swap each one for the plain word: use, help, improve, area.

  • rhetorical_qa0.83

    Does the text pose a question or fragment only to answer it immediately for dramatic effect, e.g. "The catch? It's free.", "The result? A 40% speedup."?

    Fix: Turn the question and answer into one plain statement.

  • signposting0.80

    Does the text narrate its own structure with phrases like "Let's dive in", "Here's the thing", "Let's break it down", "Here's why that matters"?

    Fix: Delete the announcement and get to the content.

  • grandiose_stakes0.80

    Does the text inflate the significance of ordinary things, e.g. "pave the way", "a testament to", "game-changer", "revolutionize", "reshape the future of"?

    Fix: Cut the inflated claim, or back it with a specific result.

  • negation_reframe0.72

    Does the text set up a contrast with a throwaway clause before making its point, e.g. "It's not X, it's Y", "Not just X, but Y", "This isn't about X. It's about Y"?

    Fix: State the point directly. Drop the "it's not X" setup.

  • hype_adjectives0.49

    Does the text pile on enthusiastic intensifiers like incredibly, truly, remarkably, powerful, amazing, stunning, without concrete support?

    Fix: Remove the intensifier, or show the evidence that earns it.

  • reflexive_triplets0.15

    Does the text habitually group things in threes (three adjectives, three parallel clauses, three-item lists) regardless of how many things there really are?

    Fix: Use as many items as there really are. Two or four is fine.

  • chatbot_artifacts0.13

    Does the text contain residue from a chat assistant, e.g. "I hope this helps", "Let me know if you'd like", "Great question!", "As an AI", "Certainly! Here's", or praise directed at the reader?

    Fix: Delete the assistant framing.

  • announced_conclusion0.12

    Does the text end by announcing that it is concluding and restating what it already said, e.g. "In conclusion", "Ultimately", "In summary", "By embracing these strategies"?

    Fix: End on the last useful point. Cut the recap.

  • hedging0.06

    Does the text pile on qualifiers that avoid committing to a position, e.g. "can potentially", "may help to", "it could be argued", "in many cases", "generally speaking"?

    Fix: Commit to the claim, or state the real uncertainty once.

  • over_structuring0.05

    Does the text impose heavy formatting (headings, bullet lists, bold labels, emoji bullets) on content that would read fine as a few paragraphs?

    Fix: Merge into paragraphs. Keep lists for real lists.

  • hollow_transitions0.02

    Does the text join sentences with filler transitions like moreover, furthermore, additionally, it's worth noting that, it's important to note, that said?

    Fix: Delete the transition, or use and, but, or so.

HOW IT WORKS

It asks a decision model yes-or-no questions about your text.

THE FACTORS

The habits it looks for, and the question it asks about each.

THE API

Send it text, get back a probability for each factor.

Base URL https://api.slop.how · no auth for now

MODELS

  • clef

    Default. Cloudflare's 27B decision model. The most precise in testing, with no false positives.

    $0.24 per million input tokens

  • clef-flash

    Clef's faster, cheaper 9B sibling. Misses a few more subtle cases.

    $0.09 per million input tokens

  • jev

    TypeSafe's Jev, via Cloudflare AI Gateway. About 6x cheaper than clef and a bit more sensitive, but flags slightly more false positives.

    $0.042 per million input tokens