Perplexity Graphify solves the most expensive part of working with someone else’s code: figuring out how it all fits together. The Graphify skill is now live in the Perplexity Computer skills marketplace, open to every Computer user, and tasks that use it are free through October 31, 2026, up to 5,000 credits per Computer user.
Reading a new codebase is slow in a specific way: you open a file, follow an import, lose the thread, and start again. Graphify’s promise is to hand the agent a map before it answers, so explanations start from the whole system instead of one file.
What Graphify actually does
Type /graphify, paste a link to a public GitHub repository, and Perplexity Computer maps the whole codebase into a knowledge graph. In that graph, files, functions, and classes become nodes, and calls and imports become edges between them.
Each edge keeps useful detail: its direction, what kind of link it is, how confident Graphify is in it, and the file and line it came from. That matters because an answer that says “this function calls that one” is only trustworthy if you can check where the claim came from. A graph with file-and-line evidence is checkable. A confident paragraph without it is not.
Computer runs the open-source Graphify engine and does the reading with its own model — nothing to install, and the mapping happens through the agent you already use.
The evidence: command, credits, and deadline
| Detail | What the announcement says |
|---|---|
| Where it lives | Perplexity Computer skills marketplace, open to every Computer user |
| How to start | Type /graphify and paste a link to a public GitHub repository |
| What the graph contains | Files, functions, and classes as nodes; calls and imports as edges |
| What each edge records | Direction, link type, confidence, and source file and line |
| Engine | Open-source Graphify engine, run by Computer; nothing to install |
| Free offer | Tasks using /graphify free through October 31, 2026, up to 5,000 credits per Computer user |
That deadline is the most important row: free through October 31 means days, not months, to test this at no task cost — and the announcement does not state what /graphify tasks will cost after that, so do not price clients as if free lasts forever.
From repo link to useful answers
1. Paste the repo — Type /graphify and share a public GitHub repository link.
2. Get the map — Computer builds the knowledge graph: files, functions, calls, and imports.
3. Ask system questions — “How does a request move through this code?” now has a map behind the answer.
4. Check the edges — Follow any claim back to its file and line before you act on it.
5. Ship the change — Make the edit with the system’s real connections in view, not just one file.
How to profit from it
A codebase map is a product, and the free-credit window is your chance to build the offer at zero task cost. Here is a concrete way to do it before October 31:
- Map five public repos in your niche this week. Pick the frameworks your clients actually use, and learn where Graphify’s map is strong and where it guesses.
- Sell a codebase onboarding audit. For a team joining a project, deliver the map plus a plain-language tour: entry points, core flows, risky dependencies, and dead code candidates.
- Offer a pre-refactor review. Before a client pays for a rewrite, show them the real dependency graph. Many “rewrites” turn out to be three tangled modules, not a whole system.
- Charge for the explanation, not the map. The map is cheap this week and may cost later. Your judgment about what to change first is the durable product.
- Document your credit use. Track how many of the 5,000 free credits each audit consumes, so you can price the same service honestly after October 31.
What to watch before you rely on it
First, confidence is not correctness. Each edge carries a confidence score, which is useful precisely because some edges will be uncertain. Treat low-confidence links as leads to verify, not facts to build on.
Second, a map is not understanding: it shows how code connects, not why a choice was made or whether a shortcut is load-bearing. Your experience fills those gaps.
Third, the free offer has a hard edge. Tasks using /graphify are free through October 31, 2026, up to 5,000 credits per Computer user. After that, the announcement gives no price. Run your pilots now, measure real credit use, and set client prices only once you know the post-October cost.
Source: The Graphify team’s announcement in the Perplexity Computer skills marketplace, linked below. Credit and deadline terms are as stated in that announcement.
Frequently Asked Questions
What is Graphify in Perplexity Computer?
It is a skill in the Computer skills marketplace that maps a codebase into a knowledge graph you can explore and ask questions about.
How do I use it?
Type /graphify and paste a link to a public GitHub repository. Computer maps the codebase using the open-source Graphify engine.
What does the knowledge graph contain?
Files, functions, and classes become nodes, while calls and imports become edges, each recording direction, link type, confidence, and source file and line.
How long is it free?
Tasks that use /graphify are free through October 31, 2026, up to 5,000 credits per Computer user, according to the announcement.
What will it cost after October 31?
The announcement does not state a post-October 31 price for /graphify tasks, so check Perplexity’s terms before quoting clients for work after that date.
Reported source: Graphify team — Perplexity can now use Graphify.
Keep Reading
Want more tools that actually pay for themselves? Browse the AI Tools section for the latest launches, pricing breakdowns, and profit playbooks — and check the official source linked above before you buy or deploy anything.