> For the complete documentation index, see [llms.txt](https://organic-1.gitbook.io/organic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://organic-1.gitbook.io/organic-docs/product/ai-scoring-agent.md).

# AI Scoring Agent

The AI Scoring Agent started as a side project to clean up crypto Twitter and grew into a core Organic tool. \
\
It evaluates posts, accounts, and task proofs against real benchmarks and spotting bot patterns, low-quality engagement, fake reach and then assigns simple scores (1–5 for “organic feel,” 0–100 for task quality). \
\
We’ll keep training it on proven projects and real milestones so it gets sharper over time. Human stewards always have final say, but the agent gives us fast, consistent signal for growth hacking tasks and contributor reviews. \
\
As it matures, we’ll offer it as a white-label service or standalone product like **Organic AI Agent** creating a new revenue stream that directly supports the community.

**What will it do**

* Scores engagements on X from 1 to 5 for organic feel
* Scores task proofs from 0 to 100
* Flags fake accounts and botted patterns
* Human stewards always have final say


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://organic-1.gitbook.io/organic-docs/product/ai-scoring-agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.