# Graphicle > Graphicle is an open-source Rust program that builds a code graph of a repository and keeps its documents, reviewed decisions and past coding-agent sessions, served to Claude Code, Codex, Cursor and other MCP clients as cited excerpts. - Canonical: https://www.anchorterminal.com/tools/graphicle - Markdown: https://www.anchorterminal.com/tools/graphicle.md (~7,450 tokens) - Slim: https://www.anchorterminal.com/tools/graphicle.min.md (~1,630 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/graphicle.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Licence: CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author. - Updated: 2026-10-15 ## Overview **Grade B · 69.8/100 · rank #178 of 1094 · #2 in Agent memory · not agent-ready · confidence medium** ## Assessment One local program gives a coding agent a code graph and project memory through 25 typed, annotated MCP tools that return cited excerpts within a token budget, with agent-written memories held for human approval. It is one day old at version 0.1.0, its SDKs are not on any registry, and the licence and advisory check fails on main. ## Facts | Field | Value | | --- | --- | | Vendor | KarLex AI, Inc. (https://www.karlex.ai/graphicle) | | Kind | MCP server | | Category | Agent memory (https://www.anchorterminal.com/categories/agent-memory) | | Transport | stdio, Streamable HTTP | | Auth | OAuth or key · No account. The stdio server (`graphicle mcp`) runs with the owner key saved in the local data folder, which reads every project in the store. Over HTTP (`graphicle serve`, 127.0.0.1:8854 by default) each agent or person gets its own access key with a role, optional expiry and optional project list, sent as `Authorization: Bearer` or `X-Workspace-Capability`, never in the URL. Keys are stored as hashes and can be revoked. | | Pricing | Free (Free · OSS) · Free under Apache-2.0 for individuals and teams, with nothing to buy. A commercial edition for teams is in private preview with no published prices. Optional model calls (answers, memory extraction, full document extraction) are paid to the provider the owner configures, or run locally through Ollama. | | x402 | No · No x402, MPP or L402 in the source, README, docs or karlex.ai (checked 2026-10-15). The software has no paid tier. | | Licence | Apache-2.0 | | Tools exposed | 25 | | Source | https://github.com/Graphicle-AI/graphicle | | Docs | https://github.com/Graphicle-AI/graphicle/blob/main/docs/quickstart.md | | llms.txt | not found | | Last release | 2026-10-14 | | GitHub stars | 144 (as of 2026-10-15) | | Surface listed | The `graphicle` program v0.1.0 and its MCP server (stdio, and HTTP through `graphicle serve`), read from the repository, docs, changelog and karlex.ai on 15 October 2026. Nothing was installed or run | | Age | One day. Repository created and v0.1.0 published on 14 October 2026; three commits on main by 15 October | | Interfaces | Command line (`setup`, `ask`, `context`, `graph`, `open`), one MCP server, a browser app, an HTTP API at `/v1/workspaces/{workspace}/repos/{repository}/commands` with `/v1/openapi.json`, and Python and TypeScript SDKs installed from source | | MCP tools | 14 read tools for recall, sources, memory and graph history, 7 code-graph tools under Graphify's names, `graph_link`, and 3 memory-proposal tools with `--allow-learning`. Optional work-state and GitHub pull-request tools | | Memory | Original sources kept word for word, reviewed decisions, preferences and procedures, and captured Claude Code and Codex turns. Reviewed memories tied to a code symbol go stale when that symbol changes | | Storage | One SQLite store in the user's data folder. Optional Neo4j, Qdrant and Redis adapters | | Models | None needed for the graph (code-only), sync, recall or MCP. Anthropic, OpenAI or Ollama for `ask` answers and memory extraction | | Connectors | GitHub, Slack, Notion, Google, Jira and Confluence in Core, each authorised by the owner | | Platforms | macOS and Linux (glibc) on arm64 and x86_64, through a Homebrew tap, an install script that checks SHA-256 and release archives. No native Windows build | | Team use | `graphicle serve` behind the owner's TLS proxy, with per-key roles, expiry and project lists. A commercial team edition is in private preview | | Benchmarks | The vendor reports a code-only Kubernetes extract in 3 min 18 s against 26 min 38 s for Graphify 0.9.88 (one exploratory run each), and a memory comparison with seven systems. Vendor measurements, not ours | | Capabilities | memory.search, memory.graph, memory.store, memory.delete | | Tags | open-source, local, self-hosted, free, no-card, apache-2.0, rust, mcp, macos, linux | | JSON | https://www.anchorterminal.com/api/v1/tools/graphicle.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-15 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 63 | 12.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 83 | 13.5 | | Agent ergonomics | 13% | 16.2 | 86 | 14.0 | | Security & auth | 14% | 17.5 | 69 | 12.1 | | Payments & pricing | 10% | 12.5 | 60 | 7.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 48 | 4.2 | | Transparency & trust (editorial 71, provenance 65) | 7% | 8.8 | 68 | 6.0 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **69.8 → B** | ### Why each score - Reliability 63: Read as local software. Installs from an official Homebrew tap, an install script that checks each archive's SHA-256, or release archives, with macOS and Linux (glibc) on arm64 and x86_64 stated. No language package registry (20). A public CI workflow formats, lints and tests each of the three crates on macOS and Linux, and every test job passed on both pushes to main. The cargo-deny job for licences, advisories and sources failed on both, and its log was not readable without a GitHub login (18). No issues filed in the project's first day. The only change since release is an outside fix for documents whose text carries a NUL byte, so the record is too short to judge (15). A dated changelog with semver crate versions, one release so far, so no breaking change to call out yet (10). Version 0.1.0, not declared stable (0). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 83: Every MCP tool has a JSON Schema input with `additionalProperties: false` and required fields marked, read from the tool list fixture in the repository (25). No llms.txt. The docs are Markdown files in the repository that an agent can read raw (5 of 10). Server instructions say which tool to use for structure and which for what the project says, `recall_project` says when to leave the reranker off, and memory tools explain draft review, while graph tools such as `query_graph` carry one-line descriptions (14 of 20). Enums on `mode`, `pack_order`, memory `kind` and `state`, length and item limits, minimum values and closed nested objects (14 of 15). Examples throughout the docs. The OpenAPI file documents 400, 403, 409 and 429 for the HTTP API and limit errors name the setting to change, but MCP error results are not catalogued (10 of 15). A dated changelog, semver and `/v1` paths (15). - Agent ergonomics 86: 25 tools with memory proposals on, which `graphicle setup` turns on by default, about 24,000 characters of definitions (15). `--tools graph` or `--tools memory` serves one half, and leaving out `--allow-learning` leaves only read tools plus `graph_link` (7 added back). `recall_project` takes `max_tokens` or `max_chars`, `include` prefixes and `skip_shown`, `query_graph` takes `token_budget` and `depth`, and `list_projects` pages with `offset` and `limit` (20). Over-limit projects are refused with a message naming the limit and its setting, 409 marks a stale revision and 429 carries Retry-After. MCP error shapes are not documented (12 of 20). Every tool carries readOnlyHint, idempotentHint and destructiveHint false, there are no destructive tools, and `propose_memory` requires an `idempotency_key` that replays the same proposal (20). Only `question` is required on recall and graph queries. Python and TypeScript SDKs exist but install only from source (8 of 15). - Security & auth 69: Read with the API checklist for a server the owner runs, as for Cognee and Graphiti. Over HTTP each person or agent gets its own key with a role, optional expiry and optional project list, stored as a hash, revocable, and sent in a header with the docs saying never in the URL. The stdio server runs with the owner key, which can read every project, and its graph tools take `repo` to reach other projects (24 of 30). The MCP server has no delete or command tool, agent writes are drafts that a person approves, and `--tools` and per-key project revocation narrow access. No approval step is needed because nothing destructive is exposed (18 of 20). Recall returns documents, connector content and captured sessions, which can carry injected text. Server instructions say memory is evidence, not tool permission, drafts need verbatim quotes, and capture redacts credentials and drops `` spans. No general prompt-injection guidance found (9 of 15). Workspace usage counters, `workflow_status` and hash-chained deletion receipts, while the team audit trail belongs to the commercial edition (6 of 15). SECURITY.md with private reporting through GitHub advisories, a valid security.txt at karlex.ai and a cargo-deny advisory check in CI that currently fails. No bug bounty or certification (10 of 20). - Payments & pricing 60: No payment protocol (0). Read with the self-hosted rule. Free under Apache-2.0 with nothing to buy (20). No card or account (20). An agent can install it and run `graphicle setup --yes` with no signup, as the README suggests (20). The commercial team edition is in private preview with no prices, so there is no paid option to score. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 48: v0.1.0 on 14 October 2026 (30). One release in the last 90 days (0). An outside pull request was merged about three and a half hours after it opened, with a maintainer reply, and Discussions and a Discord are linked. One day of history (12 of 25). Not in the official MCP registry, which returned nothing for graphicle on 15 October, and the SDKs are not published (0). Pinned GitHub Actions, dependency-graph updates and passing tests, but the licence and advisory job fails on main (6 of 10). - Transparency & trust 68: Apache-2.0 with NOTICE files that credit Graphify and every adapted project (30). The README privacy section and the FAQ list every case in which the program uses the network, say there is no telemetry or account, and keep data in one SQLite store with deletion receipts. A grep of the source for outbound hosts found only model providers, connectors and GitHub, which agrees. The karlex.ai privacy policy of 14 March 2025 covers the website, not the software (20 of 30). SECURITY.md lists supported versions. No deprecation policy (3 of 20). No telemetry to opt out of, and the network cases are disclosed, with `freshness off` and `--code-only` to limit them (18 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/graphicle.md (JSON https://www.anchorterminal.com/fixes/graphicle.json) ### What we couldn't check - Judgement call. Listed in agent-memory, not code. Its main job is recall of a project's sources and reviewed memory, beside Graphiti and Cognee, and the code graph feeds that recall. The code category covers repository platforms and library documentation. - The lead was right. The changelog calls 0.1.0 of 14 October 2026 the first public release, and the repository was created that day. The project was one day old when graded. - The lead's "SDKs" are Python and TypeScript source packages in `sdk/`, not published to PyPI or npm. - unchecked: why the cargo-deny job (licences, advisories, sources) fails. GitHub job logs need a login. - We did not install or run the program. Behaviour comes from the source, docs, tool list fixture and changelog. Speed and memory benchmark figures are the vendor's. - KarLex AI's about page says an earlier project, ASIOS, was announced in May 2025 and discontinued. ### Sources - repository README, LICENSE, NOTICE.md and SECURITY.md: (seen 2026-10-15) - changelog (0.1.0, 14 October 2026, first public release): (seen 2026-10-15) - GitHub release v0.1.0 and assets: (seen 2026-10-15) - MCP server docs and tool list: (seen 2026-10-15) - published tool list fixture (25 tools, schemas, annotations, server instructions): (seen 2026-10-15) - tool contract builder and recall schema: (seen 2026-10-15) - HTTP API and OpenAPI document: (seen 2026-10-15) - program README (editions, accounts and permissions, hosted use): (seen 2026-10-15) - team server guide: (seen 2026-10-15) - FAQ (network use, Graphify port): (seen 2026-10-15) - configuration (retrieval, limits, freshness): (seen 2026-10-15) - CI workflow: (seen 2026-10-15) - CI runs and jobs: (seen 2026-10-15) - issues and pull requests: (seen 2026-10-15) - Python SDK manifest (not on PyPI): (seen 2026-10-15) - Homebrew formula: (seen 2026-10-15) - Graphicle page at KarLex AI: (seen 2026-10-15) - KarLex AI about page: (seen 2026-10-15) - terms of use: (seen 2026-10-15) - privacy policy: (seen 2026-10-15) - security.txt: (seen 2026-10-15) - official MCP registry search (no entry): (seen 2026-10-15) - RDAP for karlexai.com: (seen 2026-10-15) ## Who's behind it (provenance 65/100, checked 2026-10-15) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | KarLex AI, Inc. | 20/20 | | Domain age | karlex.ai, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | no hosted endpoint | n/a | | Terms of service | read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points | 5.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The README and LICENSE read Copyright 2026 KarLex AI, Inc. karlex.ai names KarLex AI as the company behind Graphicle and links the graphicle-ai GitHub organisation, created on 29 September 2026. The terms of use and privacy policy at karlex.ai are dated 14 March 2025 and cover the website and its accounts, not the Graphicle software, which runs on the user's machine. karlex.ai/.well-known/security.txt names security@karlexai.com and expires on 7 April 2027 (read 15 October 2026). karlexai.com redirects to karlex.ai; RDAP at Verisign gives karlexai.com a registration date of 20 December 2023. The .ai registration date was not read. karlex.ai's robots.txt allows all crawlers. The software runs on the owner's machine, so there is no vendor endpoint or status page to check. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.karlex.ai/legal/terms), read 2026-10-15, dated 2025-03-14, states 6 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "(c) you shall not access the Site in order to build a similar or competitive website, product, or service" - To know. Says the terms or the service can change without notice (costs points). "Company reserves the right, at any time, to modify, suspend, or discontinue the Site (in whole or in part) with or without notice to you." - To know. Says access can be ended without notice or for any reason. "We may suspend or terminate your rights to use the Site (including your Account) at any time for any reason at our sole discretion, including for any use of the Site in violation of these Terms." - To know. Requires arbitration or waives class actions. "AMONG OTHER THINGS, SECTION 8.2 INCLUDES AN AGREEMENT TO ARBITRATE WHICH REQUIRES, WITH LIMITED EXCEPTIONS, THAT ALL DISPUTES BETWEEN YOU AND US SHALL BE RESOLVED BY BINDING AND FINAL ARBITRATION." - Gives the date it was last updated. Last updated 2025-03-14. - Names the governing law or courts. Disputes go to the courts of the State of Delaware. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Says how changes to the terms are announced. Gives 30 days of notice before a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-15). Total liability to the user for any damages under the terms is limited to 50 US dollars. "OUR LIABILITY TO YOU FOR ANY DAMAGES ARISING FROM OR RELATED TO THESE TERMS (FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION), WILL AT ALL TIMES BE LIMITED TO A MAXIMUM OF FIFTY US DOLLARS." - Also in the text (2026-10-15). The licence to use the site and its account functions is limited to personal, noncommercial use. "Subject to these Terms, Company grants you a non-transferable, non-exclusive, revocable, limited license to use and access the Site solely for your own personal, noncommercial use." **Privacy policy** (https://www.karlex.ai/legal/privacy), read 2026-10-15, dated 2025-03-14, states 8 of the 8 things a reader expects. - To know. Says it may use customer content to train or improve models, and gives an opt-out. "To improve our services, KarLex AI may use anonymised, de-identified data submitted through our tools to train and fine-tune our models. We do not use personal or sensitive information for training purposes, and users can opt out of data sharing at any time through their account settings." - Gives the date it was last updated. Last updated 2025-03-14. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. Gives an email address, hidden from our reader by the page. - Says where data is transferred or stored. Data goes to the United States. - Also in the text (2026-10-15). The policy places no limit on using or disclosing non-personal information, including to partners and advertisers. "This Privacy Policy does not limit in any way our use or disclosure of Non-Personal Information and we reserve the right to use and disclose such Non-Personal Information to our partners, advertisers and other third parties at our discretion." ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - 25 MCP tools with closed JSON Schema inputs, enums and limits, readOnlyHint on every read tool, and an idempotency key on `propose_memory` - Recall returns excerpts with file, line range and hash, within a `max_tokens` budget, and `skip_shown` avoids resending excerpts - Agent-proposed memories need verbatim quotes and a person's approval, and the MCP server has no tool that deletes or runs commands - No telemetry or account. The source calls out only to models, connectors and GitHub that the owner configures - Apache-2.0 with detailed NOTICE files, a SECURITY.md with private GitHub reporting and a valid security.txt at karlex.ai ## Weaknesses - One release, v0.1.0 on 14 October 2026, from a repository created that day - The cargo-deny licence and advisory job failed on both pushes to main, though the test jobs passed on macOS and Linux - The stdio server runs with the owner key, so its graph tools can read any project in the store unless an HTTP key is scoped - SDKs are source-only, no llms.txt, not in the official MCP registry, and no native Windows build - The team audit trail is in the commercial edition. Core shows usage counters and deletion receipts only ## Before you call it (notes for agents) 1. Call `recall_project` with a `max_tokens` budget, then `read_project_source` with the cited id and byte offset to continue a cut excerpt 2. Use `query_graph`, `get_neighbors` and `shortest_path` for structure questions, and pass `repo` to reach another synced project 3. Treat proposed memories as drafts. They are not served until a person approves them in `graphicle open` under Memory 4. Ask the user before running `graphicle setup`, which edits agent settings, AGENTS.md and Git hooks, and use `graphicle disconnect` to undo it 5. Over HTTP send the key as `Authorization: Bearer`, never in the URL, and on 429 wait for the Retry-After reset ## Connect Install: ```bash brew install graphicle-ai/tap/graphicle && cd your-repo && graphicle setup ``` Claude Code: ```bash graphicle sync . && graphicle connect claude-code ``` MCP client configuration: ```json { "mcpServers": { "graphicle": { "args": [ "mcp", "--project", "PROJECT_ID" ], "command": "/full/path/to/graphicle" } } } ``` Through letme (picks today, calling later): https://letme.dev/graphicle. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Zep | B | 69.3 | 200 | memory.store, memory.search, memory.graph, memory.delete | no | https://www.anchorterminal.com/tools/zep.md | | Supermemory API + MCP | B | 63.6 | 413 | memory.store, memory.search, memory.graph, memory.delete | no | https://www.anchorterminal.com/tools/supermemory.md | | Mem0 Platform + MCP | C | 56.1 | 685 | memory.store, memory.search, memory.graph, memory.delete | no | https://www.anchorterminal.com/tools/mem0.md | | Cognee | C | 54.6 | 730 | memory.store, memory.search, memory.graph, memory.delete | no | https://www.anchorterminal.com/tools/cognee.md | | Graphiti | D | 53.3 | 761 | memory.store, memory.search, memory.graph, memory.delete | no | https://www.anchorterminal.com/tools/graphiti.md | | Amazon Bedrock AgentCore Memory | A | 79.4 | 12 | memory.store, memory.search, memory.delete | no | https://www.anchorterminal.com/tools/agentcore-memory.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - v0.1.0 on 14 October 2026, which the changelog calls "the first public release". The repository was created the same day (source: ) - The code-graph engine is a Rust port of Graphify, kept compatible with Graphify 0.9.88 and credited in NOTICE. The memory, app and session capture are Graphicle's own (source: ) - One MCP server with 25 tools when memory proposals are on (the default after `graphicle setup`), each with a closed JSON Schema input and readOnlyHint annotations. `--tools graph` or `--tools memory` serves one half (source: ) - Memories an agent proposes are drafts. Every quote must appear word for word in a current source, and a person approves each draft in the app before recall uses it (source: ) - `graphicle setup` edits agent settings, `.mcp.json`, `AGENTS.md` and Git hooks, backs up each file first and lists what it changed. `graphicle disconnect` undoes it (source: ) - The Python and TypeScript SDKs are source packages in `sdk/` and are not on PyPI or npm yet. The PyPI name graphicle belongs to an unrelated physics library (source: ) - #2 of 11 in Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md - All 65 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md ## Compare - [Amazon Bedrock AgentCore Memory vs Graphicle](https://www.anchorterminal.com/compare/agentcore-memory-vs-graphicle.md): A 79.4 vs B 69.8 - [Cognee vs Graphicle](https://www.anchorterminal.com/compare/cognee-vs-graphicle.md): C 54.6 vs B 69.8 - [Graphicle vs Graphiti](https://www.anchorterminal.com/compare/graphicle-vs-graphiti.md): B 69.8 vs D 53.3 - [Graphicle vs Hindsight](https://www.anchorterminal.com/compare/graphicle-vs-hindsight.md): B 69.8 vs D 50.2 - [Graphicle vs Honcho](https://www.anchorterminal.com/compare/graphicle-vs-honcho.md): B 69.8 vs B 64.1 - [Graphicle vs Khoj](https://www.anchorterminal.com/compare/graphicle-vs-khoj.md): B 69.8 vs E 38.5 - [Graphicle vs LangMem](https://www.anchorterminal.com/compare/graphicle-vs-langmem.md): B 69.8 vs D 47.9 - [Graphicle vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/graphicle-vs-mem0.md): B 69.8 vs C 56.1 - [Graphicle vs Supermemory API + MCP](https://www.anchorterminal.com/compare/graphicle-vs-supermemory.md): B 69.8 vs B 63.6 - [Graphicle vs Zep](https://www.anchorterminal.com/compare/graphicle-vs-zep.md): B 69.8 vs B 69.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on karlex.ai or one of its subdomains, or the README of github.com/Graphicle-AI/graphicle. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "graphicle", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Graphicle on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Graphicle on Anchor Terminal](https://www.anchorterminal.com/badges/graphicle.svg)](https://www.anchorterminal.com/tools/graphicle) ``` Plain link: ```html Graphicle on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Graphicle is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/graphicle-dark.png - Light: https://www.anchorterminal.com/assets/share/graphicle-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=graphicle