chaxus.com valid
Online Document Editor
A free, privacy-first document editor that runs entirely in the browser. Edit
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://edit.chaxus.com/llms.txt
- llms-full.txt
- https://edit.chaxus.com/llms-full.txt
- Sections
- 6
- Links
- 35
- Size
- 11180 bytes
- Registered
- 2021-10-28
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-26T15:54:41.274Z
- Last checked
- 2026-10-26T15:55:05.776Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T15:54:41.281Z. Cached copy · Source on chaxus.com
# Online Document Editor
> A free, privacy-first document editor that runs entirely in the browser. Edit
> Microsoft Word (DOCX), Excel (XLSX), PowerPoint (PPTX) and CSV files, and open
> PDF files, with no required document upload or sign-up. Core editing and
> conversion happen on the user's device. Offline use requires the relevant
> resources to be cached. The optional AI assistant is off by default. Embedding hosts and external browser agents have separate
> data flows, described below.
## What it does
- Edit DOCX, XLSX, PPTX and CSV files directly in the browser.
- Also opens the OpenDocument formats (ODT, ODS, ODP) and the legacy binary
formats (DOC, XLS, PPT), plus RTF and TXT, and can save back to them.
- Export DOCX, XLSX, PPTX, ODT, ODS and ODP to PDF locally.
- Open and view PDF files in the browser (dedicated PDF editor, no upload).
- Core file opening, editing and conversion run client-side without a required upload.
- The writing assistant (rewrite / summarize / translate a selection) sends text
only to the destination the user configures: a loopback service on the user's
own machine keeps it on the device, while a cloud endpoint the user configures
with their own API key receives the selected text and the instruction. With no
destination configured, the browser-local models are used only after an explicit
opt-in, because they did not pass the project's seven-language writing quality
acceptance.
- No account, no sign-up, and no server required.
- Open a document from a URL via the `?src=` or `?file=` query parameter.
- Installable as a PWA; previously cached editing resources can work offline.
An initial visit does not guarantee every format, font or engine is cached.
- Saves back into the file the user picked, rather than downloading a new copy
each time: the first save chooses the file, every save after it writes to that
file. Requires the File System Access API, so Chromium browsers only; Safari
and Firefox fall back to a download. Nothing is uploaded either way -- the
write goes from the browser to the user's own disk.
- When autosave is enabled, recovery copies are written into the visitor's own
browser (IndexedDB). Reopening the editor can offer a retained copy, and the
document id in the URL can restore it on reload. Closing a tab does not delete
these copies. Browser storage can be cleared or evicted and edits not yet
autosaved can be lost; save the file separately rather than relying on recovery.
- Those copies stay on the device for 7 days after the last edit or open, then
delete themselves. A `/history` page lists what is stored, with per-document
delete and a delete-all, and autosave can be switched off there. Nothing is
uploaded -- the copies exist only in that browser, on that device.
- Embeddable into other websites through a postMessage API (iframe integration),
including a runtime read-only mode that can be toggled from the parent page.
- Reads CSV files in legacy encoding
…Machine-readable: GET /v1/resolve?q=chaxus.com · GET /v1/domain/chaxus.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage chaxus.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for chaxus.com:
1. POST https://agentwebmap.com/v1/sites/chaxus.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://chaxus.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/chaxus.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/chaxus.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.