docs: add AI agents guide#995
Open
vdusek wants to merge 8 commits into
Open
Conversation
vdusek
added
adhoc
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #995 +/- ##
==========================================
- Coverage 91.75% 91.69% -0.07%
==========================================
Files 50 50
Lines 3215 3215
==========================================
- Hits 2950 2948 -2
- Misses 265 267 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
vdusek
force-pushed
the
docs/ai-agents-guide
branch
2 times, most recently
from
84b618c to
1bb3288
Compare
vdusek
force-pushed
the
docs/ai-agents-guide
branch
from
1bb3288 to
034a077
Compare
szaganek
approved these changes
Jul 6, 2026
|
|
||
| An agent becomes useful once it can act on the world. On Apify, any of the thousands of Actors in the [Apify Store](https://apify.com/store) can become a tool: a scraper that fetches data, a browser automation that fills a form, or an API wrapper that posts a message. | ||
|
|
||
| Some frameworks ship a ready-made wrapper for this. For LangGraph and other [LangChain](https://www.langchain.com/)-based agents, the [`langchain-apify`](https://github.com/apify/langchain-apify) package exposes any Actor as a tool with a single line: |
Contributor
There was a problem hiding this comment.
We can't leave a single this dangling like that, we need to specify what this is.
|
|
||
| ## Running on the Apify platform | ||
|
|
||
| Agents run on the standard [Apify Python base image](https://hub.docker.com/r/apify/actor-python), so no browser or extra system dependencies are needed. Add `apify` and the packages shown in your framework's section above to `requirements.txt`, then deploy the Actor as usual. |
Contributor
There was a problem hiding this comment.
Suggested change
| Agents run on the standard [Apify Python base image](https://hub.docker.com/r/apify/actor-python), so no browser or extra system dependencies are needed. Add `apify` and the packages shown in your framework's section above to `requirements.txt`, then deploy the Actor as usual. | |
| Agents run on the standard [Apify Python base image](https://hub.docker.com/r/apify/actor-python), so no browser or extra system dependencies are needed. Add `apify` and the packages required by your framework to `requirements.txt`, then deploy the Actor as usual. |
Please verify my guess. I honestly don't know what section it refers to.
# Conflicts: # README.md # docs/01_introduction/index.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a guide on hosting AI agents as Apify Actors.
Each of the five supported frameworks (LangGraph, CrewAI, PydanticAI, LlamaIndex, and Smolagents) gets a complete, runnable single-file Actor example. Every example routes its LLM calls through the Apify OpenRouter proxy, so no provider API key is needed and each one runs as a "Run on Apify" example. The guide also covers choosing a framework, connecting to an LLM, using Apify Actors as agent tools, and monetizing with pay-per-event. Every framework links to its matching Actor template.
The new guide is also linked from the README, the overview, and the quick start.