# ONES vs Roma (slim)

> Roma scores 48.7 (D) to ONES's 46.9 (D) for issues and tasks. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/ones-vs-roma.md (~4,950 tokens) · this version ~2,980 tokens · JSON https://www.anchorterminal.com/compare/ones-vs-roma.json · canonical https://www.anchorterminal.com/compare/ones-vs-roma
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Roma scores 48.7 (D) on agent readiness against ONES's 46.9 (D), and leads in 3 of 7 scored categories. ONES leads on security & auth, payments & pricing and maintenance & community. Both do issues and tasks.

- ONES: D 46.9, rank #1164 of 1510 · https://www.anchorterminal.com/tools/ones.min.md
- Roma: D 48.7, rank #1119 of 1510 · https://www.anchorterminal.com/tools/roma.min.md
- ONES, good for Teams moving off Jira and Confluence who want issues, sprints, worklogs, test cases and a wiki in one tool an agent can reach. Ahead on Security & auth, 65 against 44; Payments & pricing, 30 against 20; Maintenance & community, 68 against 57. Also Free to start without a card; No incidents deducted, where Roma loses 3 points for them.
- Roma, good for One person, or a few people sharing lists, who want an AI chat to read and write their tasks, notes and typed lists, with a single orientation call and change events for a worker agent. Ahead on Reliability, 40 against 25; Schema & documentation, 83 against 55; Agent ergonomics, 60 against 40.

| Category | ONES | Roma |
| --- | --- | --- |
| Reliability (16%) | 25 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 55 | 83 |
| Agent ergonomics (13%) | 40 | 60 |
| Security & auth (14%) | 65 | 44 |
| Payments & pricing (10%) | 30 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 57 |
| Transparency & trust (7%) | 62 | 60 |

| Fact (where they differ) | ONES | Roma |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | The Beautiful ONES Technology PTE. LTD. | Milo Mode Inc. |
| Hosted endpoint | `https://us.ones.com/mcp` | `https://api.roma.app/mcp` |
| Transports | Streamable HTTP | Streamable HTTP, HTTP |
| Pricing | Freemium | Free |
| Licence | none | Proprietary service under Roma's terms of service. No public source repository found |
| Tools exposed | 67 | 32 |
| MCP registry | `com.ones/ones` | not listed |
| Last release | 2026-09-30 | 2026-10-28 |
| Terms last updated | 2025-09-08 | 2026-09-18 |
| Privacy policy last updated | 2026-01-07 | 2026-10-06 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |

Why the edge:
- Schema & documentation, Roma +28: ONES 55 (No downloadable OpenAPI file was found. The reference is rendered pages, and the MCP docs list tool names and one-line descriptions without input schemas (0). llms.txt with sized indexes and a Markdown copy of every page (10). Endpoint and tool descriptions state what each does in one line, with version history per endpoint but little on when not to use one (10 of 20). Parameters are typed with defaults, limits (`limit` at most 100) and required marks (10 of 15). Each endpoint lists 200, 401, 403, 404 and 500 responses with schemas and examples (10 of 15). API version 2.0, a History table per endpoint and dated release notes (15). 0 + 10 + 10 + 10 + 10 + 15 = 55.); Roma 83 (The generated tool reference gives every one of the 32 MCP tools typed parameters with required flags and a result shape, and the REST API page links an OpenAPI document for its 39 operations at api.roma.app/api/v1/openapi.json (the file per the 8 October check, not re-read on 4 November). A live `tools/list` needs an account (25). llms.txt, llms-full.txt and a Markdown copy of every docs page (10). Descriptions say what a tool is for, when to call it and in several cases when not to, such as `get_item` being the call to show one item and `run_automation` only on the person's request (17). Enums for status stages, sort, mode and kind, length and item limits, and required fields. Ids and timestamps are plain strings with no format, and filter clauses and property values are open objects (11). Each tool has an example call, but most pass empty or placeholder arguments. Six error codes and five statuses are documented (8). The REST path is versioned as v1 and the MCP changelog is dated, newest 28 October 2026. Its 13 October entry retired 24 tools with no alias on the day (12).)
- Security & auth, ONES +21: ONES 65 (OAuth for MCP clients with per-scope consent, Personal API keys created with chosen scopes and shown once, organisation credentials, token introspection and revocation, all sent as Bearer headers (30). Scope groups allow a read-only grant, and the docs advise revoking unused clients, but writes run without a confirmation step and the consent page preselects every group (12 of 20). Tools return issue, comment and wiki text written by other users plus `search_external_web` results, and no prompt-injection guidance was found (0). The authorised client list shows each client's grant time and last active time, and on-premises installs document an audit log (8 of 15). security.txt valid until June 2027, and the trust centre lists SOC 2 Type II, ISO 27001 and ISO 27018 without report access or a bug bounty (15 of 20). 30 + 12 + 0 + 8 + 15 = 65.); Roma 44 (OAuth 2.1 with PKCE and dynamic client registration, one-hour access tokens and refresh tokens, or one API key per account stored as a hash and revocable in settings. The docs state that scopes do not narrow access, so each credential has the person's whole workspace, and revoking an OAuth grant on Roma's side means emailing the vendor. Scored as plain revocable keys (20). No read-only credential. Protection rests on tool badges that clients act on, a consent screen naming what the app can reach, `confirmReplace` for body replacement, a preview before a lossy move or retype (`acknowledgeDataLoss`) and a 30-day trash for every delete (10). Item bodies, items other people share, memory entries and automation run output can hold text from other people, `run_automation` can act through the person's connected apps and `manage_triggers` sends item data to an outside address. The docs mark both as reaching outside Roma, but no prompt-injection guidance was found (3). Writes through the connection are marked in the person's event log, `read_log` reads an item's log, and body edits are versioned with `restore_version`. No per-call log of reads was found (9). No security.txt (404 on 4 November 2026), disclosure policy, bug bounty or certification found. The privacy policy has a general security paragraph (2).)
- Agent ergonomics, Roma +20: ONES 40 (Scored on the MCP server and the Open API together. 67 MCP tools load by default (5), and a client granted fewer scope groups is limited to fewer tools (5 back). Lists take `limit` and `cursor` with project and issue type filters, and `query_issues_by_onesql` runs a filtered query (15 of 20). Error status codes are documented per endpoint with response schemas, but no error code catalogue was found (8 of 20). No idempotency keys or MCP annotations found (0). One official SDK, `@ones-open/node-sdk`, aimed at ONES Apps, and the MCP setup is one `mcp-remote` line (7 of 15). 10 + 15 + 8 + 0 + 7 = 40.); Roma 60 (32 MCP tools load at once, which scores 5 for more than 30. No toolsets or read-only subset on the server, so nothing added back (5). `limit` on the list tools, time windows, status filters and `sort` on `list_items`, `offset` paging with count and sum modes on `query_items`, and since 13 October a `changedSince` cursor with `hasMore` and deletions as tombstones. `list_items` without the cursor still stops at 200 rows and `search` at 20 with no paging, so the line is still partly met. The earlier partial is kept (14). Errors are one sentence saying what to change, with six REST codes and `isError: true` on MCP (16). Every tool carries a badge (16 read-only, 5 adding data, 11 updating or removing), 10 are marked safe to retry, and `externalId` and `matchOn` guard `create_items`. `create_list`, `create_expert` and `create_image_upload` have no idempotency key (17). An item needs only a title, body writes append by default and `get_context` orients a session in one call. No SDK in any language (8).)
- Reliability, Roma +15: ONES 25 (Graded as a hosted service on ONES.com Cloud's Open API and MCP server. No status page is linked from ones.com, the trust centre or the docs, and status.ones.com did not resolve (0). With no readable history the incident line scores 5. No rate limit with numbers was found in the developer docs index or the terms, which only reserve the right to restrict excessive traffic (0). No 429, backoff or idempotency guidance found (0). The pricing page states 99.9% uptime on Business and 99.95% on Enterprise (10). The MCP server has been in the release notes since 6.42.0 on 26 August 2025 and carries no beta label (10). 0 + 5 + 0 + 0 + 10 + 10 = 25.); Roma 40 (Graded on the hosted MCP server and its REST twin, with the hosted lines. No status page is linked from roma.app, its llms.txt or llms-full.txt, and status.roma.app did not connect through our network on 4 November 2026 (0). With no page there is no incident history to read (0). The limit is published as 60 requests a minute per token or key (15). 429 carries `Retry-After` and the docs say to wait for it, and the core write, `create_items`, takes an `externalId` per entry so a re-sent batch returns the items already made, with `messageKey` on `post_chat_message` too. Up from 13, which isn't a value on this line, now that the write without a key (`create_task`) is gone (15). No SLA, and the terms supply the service as is (0). The developer docs carry no beta or preview label on the server or the API. The Beta mark sits on the operator's browser inside the app (10).)
- Maintenance & community, ONES +11: ONES 68 (Latest dated release notes are 7.33.0 on 30 September 2026, 37 days before this check. The registry entry moved to 1.0.3 on 8 October with no release note behind it, so it doesn't set recency (20). Nine dated releases since 8 August, several adding Open API endpoints or MCP capabilities (7.23.0, 7.26.0, 7.27.0, 7.29.0) (20). Closed service with a public changelog and support by email, with no public issue tracker (8 of 15). Verified com.ones/ones namespace in the official MCP registry (15). One official SDK for apps, with package health not checked (5 of 10). 20 + 20 + 8 + 15 + 5 = 68.); Roma 57 (The MCP changelog's newest entry is 28 October 2026, seven days before this check (30). Ten dated MCP changelog entries in the 90 days from 6 August (13 and 14 August, 4, 18, 23 and 30 September, 2, 13, 26 and 28 October 2026), and a weekly product changelog, newest 3 November 2026 (20). Support is an email address, hello@roma.app, with accounts on X and LinkedIn. No forum, issue tracker or public repository was found, so replies could not be read (7). No readable official MCP registry page names Roma, and no SDKs (0). No public packages or CI to assess (0).)
- Payments & pricing, ONES +10: ONES 30 (No x402, MPP or L402 (0). Plan prices are public per seat a year, with nothing per call (10). The free plan covers up to 30 seats and the pricing page says no card is needed (20). A person signs up in a browser and grants OAuth consent (0). 0 + 10 + 20 + 0 = 30.); Roma 20 (No x402, MPP or L402 in the docs or the terms (0). No price is published anywhere on roma.app, and the terms have no fees clause (0). The developer docs answer whether connecting an agent needs a paid plan with a Roma account and nothing else, so we scored a free tier. We did not sign up to confirm that no card is asked for (20). A person creates the account and approves OAuth, or copies a key, in a browser or the app (0).)