{ "data": { "a": { "slug": "cozi", "name": "Cozi Family Organizer", "vendor": "Cozi, Inc.", "vendorUrl": "https://www.cozi.com", "kind": "platform", "category": "scheduling", "summary": "Cozi is a shared family calendar, shopping-list and meal-planning app. Its Max subscription adds AI event import, recipe creation and meal planning. Official calendar sharing uses read-only feeds.", "url": "https://www.anchorterminal.com/tools/cozi", "markdownUrl": "https://www.anchorterminal.com/tools/cozi.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cozi.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cozi.json", "dns": "cozi.grade.anchorterminal.com", "license": "Proprietary service; see governing terms and the access limitations below.", "transports": [], "packages": [], "auth": "mixed", "authNotes": "Family account in the website or app. Official iCalendar feeds can be shared or subscribed to read-only. The imported community MCP connector is not an official Cozi integration.", "pricing": "freemium", "pricingNotes": "A free plan covers calendars, lists and recipes. Cozi Max is advertised at $79.99 a year. No official public write-API pricing was found.", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 route established in the documentation reviewed on 19 October 2026.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-19" }, "docsUrl": "https://www.cozi.com/using-cozi-with-other-calendars/", "capabilities": [ "calendar.read", "calendar.share" ], "tags": [ "scheduling", "platform", "freemium", "access-unverified", "not-for-agents" ], "graded": true, "anchor": { "graded": true, "score": 16.1, "grade": "F", "agentReady": false, "rank": 1312, "ranked": true, "rankOf": 1349, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 10, "maintenance": 0, "payments": 30, "reliability": 15, "schema": 15, "security": 10, "transparency": 40 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-19" }, "negative": 0, "verdict": "Documented read-only calendar exchange. No official external-agent write API verified.", "bestFor": "Cozi is a shared family calendar, shopping-list and meal-planning app.", "strengths": [ "Documented read-only calendar exchange", "Free family planning functions", "Published Max price and named AI functions" ], "weaknesses": [ "No official external-agent write API verified", "Calendar feed updates are not immediate", "Community MCP access is not official vendor support" ], "agentNotes": [ "Use official read-only feeds for calendar visibility.", "Make edits in the originating calendar and allow for the refresh delay." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 16.1 } ], "editorialScores": { "ergonomics": 10, "maintenance": 0, "payments": 30, "reliability": 15, "schema": 15, "security": 10, "transparency": 35 }, "provenanceScore": 45, "checked": { "categories": { "ergonomics": "2026-10-19", "maintenance": "2026-10-19", "payments": "2026-10-19", "reliability": "2026-10-19", "schema": "2026-10-19", "security": "2026-10-19", "transparency": "2026-10-19" }, "last": "2026-10-19", "lastMoved": "2026-10-27", "oldest": "2026-10-19", "stale": false, "staleAfterDays": 90 } }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/cozi" }, "area": "everyday", "provenance": { "legalEntity": "Cozi, Inc.", "domain": "cozi.com", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://www.cozi.com/terms-of-use/", "privacy": "https://www.cozi.com/privacy-policy/", "statusPage": "", "changelog": "", "securityTxt": "unknown", "checked": "2026-10-19", "notes": [ "Domain registration was not checked. No ownership claim was verified." ], "score": 45 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cozi.json", "live": { "slug": "cozi", "securityTxt": { "url": "https://cozi.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:16.978784151Z" }, "domain": { "domain": "cozi.com", "registered": "1997-10-19", "source": "https://rdap.verisign.com/com/v1/domain/cozi.com", "checkedAt": "2026-11-01T14:10:59.424730314Z" }, "pages": [ { "url": "https://www.cozi.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:39:06.917824959Z", "changedAt": "2026-11-03T08:04:56.247182804Z", "fingerprint": "f40f3fa45c66" }, { "url": "https://www.cozi.com/terms-of-use/", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:39:09.640386204Z", "changedAt": "2026-11-03T08:04:59.483702065Z", "fingerprint": "4b2e3573a8bb" } ], "updatedAt": "2026-11-04T15:53:16.978784151Z" } }, "answer": "SavvyCal API + MCP scores 57 (C) on agent readiness against Cozi Family Organizer's 16.1 (F), and leads in 6 of 7 scored categories.", "b": { "slug": "savvycal", "name": "SavvyCal API + MCP", "vendor": "SavvyCal, Inc.", "vendorUrl": "https://savvycal.com", "kind": "http-api", "category": "scheduling", "summary": "SavvyCal's scheduling API lists and books events on scheduling links, reads open time slots and manages links, webhooks and workflows, with a hosted MCP server that lets an assistant book, move and cancel meetings.", "url": "https://www.anchorterminal.com/tools/savvycal", "markdownUrl": "https://www.anchorterminal.com/tools/savvycal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/savvycal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/savvycal.json", "dns": "savvycal.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.savvycal.com/v1", "packages": [], "auth": "mixed", "authNotes": "Personal access tokens (`pt_secret_...`) made in Settings \u003e Developers, or OAuth 2 authorisation code apps registered there, both sent as `Authorization: Bearer`. OAuth access tokens last 2 hours with a refresh token, and the spec declares no scopes for either. The MCP server at https://savvycal.com/mcp signs in with OAuth 2.1 (PKCE S256, dynamic client registration, scopes `mcp:read` and `mcp:write`, a revocation endpoint) and needs no key.", "pricing": "freemium", "pricingNotes": "The API, webhooks and the MCP server are on every plan including Free, per the plans page. Free accounts connect calendars, make links and run polls, but people can only book a link on Basic ($12 a user a month, $120 a year) or Premium ($20 a user a month, $200 a year). No self-serve trial, a 30-day money-back guarantee instead, and no card is mentioned for Free. 25 per cent off for students, educators and nonprofits.", "priceSummary": "$12 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI spec at api.savvycal.com/v1/spec or the pricing page (checked 2026-11-03). The spec has no 402 response.", "endpoints": [] }, "toolCount": 63, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.savvycal.com/developers", "llmsTxt": "https://docs.savvycal.com/llms.txt", "openapi": "https://api.savvycal.com/v1/spec", "capabilities": [ "calendar.booking", "calendar.availability", "calendar.read", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "oauth", "llms-txt", "openapi", "webhooks", "status-page", "security-txt", "closed-source" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 57, "grade": "C", "agentReady": false, "rank": 726, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 40, "payments": 30, "reliability": 70, "schema": 74, "security": 50, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.", "bestFor": "An agent booking on a person's SavvyCal links or driving their account through the MCP server.", "strengths": [ "OpenAPI 3.0.0 spec at api.savvycal.com/v1/spec, llms.txt and a Markdown twin of every docs page", "Hosted MCP server with OAuth 2.1, PKCE, dynamic client registration and `mcp:read` and `mcp:write` scopes, included on every plan", "Webhooks signed with HMAC-SHA256, retried up to 20 times with exponential backoff, over 16 event types", "Status page with calendar connection components and no notices from June to November 2026", "The MCP docs say the assistant asks for confirmation before cancelling meetings, deleting links or inviting teammates" ], "weaknesses": [ "No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)", "No idempotency keys, Retry-After header or official SDK", "No SOC 2 or ISO 27001 certification and no bug bounty, per the security page", "OAuth apps and personal access tokens carry no scopes, so a REST token reaches everything the user can", "Only one dated product update in the 90 days to 3 November 2026, and no API changelog" ], "agentNotes": [ "Call GET /v1/links/{link_id}/slots with `from` and `until` (at most 31 days apart) and book only a returned slot; POST /v1/links/{link_id}/events refuses other times with 422", "Keep event creation under 10 requests a minute per link, failed attempts included, or expect 429 with no Retry-After", "Page with the `after` and `before` cursors from `metadata` and `limit` up to 100; an invalid filter value resets every filter to its default", "Connect the MCP server with a client that supports dynamic client registration, and request `mcp:read` when the task only reads", "Verify webhooks with HMAC-SHA256 over the raw body against `x-savvycal-signature` and answer 2xx quickly" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57 } ], "editorialScores": { "ergonomics": 53, "maintenance": 40, "payments": 30, "reliability": 70, "schema": 74, "security": 50, "transparency": 57 }, "provenanceScore": 89, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.savvycal.com/v1/me -H \"Authorization: Bearer $SAVVYCAL_TOKEN\"", "claudeCode": "claude mcp add --transport http savvycal https://savvycal.com/mcp", "config": { "mcpServers": { "savvycal": { "url": "https://savvycal.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/calendar.booking", "tool": "https://letme.dev/savvycal" }, "area": "everyday", "unitPrices": [ { "item": "Basic", "unit": "seat-month", "usd": 12, "note": "$120 a user a year billed annually" }, { "item": "Premium", "unit": "seat-month", "usd": 20, "note": "$200 a user a year billed annually" } ], "provenance": { "legalEntity": "SavvyCal, Inc.", "domain": "savvycal.com", "domainRegistered": "2020-08-12", "endpointOnVendorDomain": true, "terms": "https://savvycal.com/terms", "privacy": "https://savvycal.com/privacy", "statusPage": "https://savvycal.instatus.com", "changelog": "https://feedback.savvycal.com/updates", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The terms (last updated 21 January 2026) name SavvyCal, Inc. under Minnesota law with AAA arbitration. They forbid access through automated or non-human means and the use of bots, scrapers or data-extraction tools, and do not mention the API, which the separate developer docs cover. Recorded as a fact; the public pages were read.", "savvycal.com/robots.txt disallows /events/ for every crawler, names ClaudeBot and anthropic-ai among twelve AI crawlers with the same rule, and sets Content-Signal ai-train=no, search=yes, ai-input=yes. docs.savvycal.com allows all with ai-train=yes. Nothing under /events/ was fetched.", "The privacy policy (17 October 2026) names SavvyCal, Inc., US servers, Stripe, OpenAI for advertising measurement, and a DPA with Standard Contractual Clauses. The DPA page is dated 16 January 2023.", "RDAP gives savvycal.com a registration date of 12 August 2020.", "security.txt at savvycal.com/.well-known/security.txt names security@savvycal.com, expires 2 May 2027 and points to savvycal.com/security.", "The status page is savvycal.instatus.com (Instatus), linked from the site footer. The What's New board at feedback.savvycal.com/updates is the product changelog." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/savvycal.json", "live": { "slug": "savvycal", "probe": { "target": "https://api.savvycal.com/v1", "method": "get", "lastAt": "2026-11-04T22:02:57.017408527Z", "lastOk": true, "lastStatus": 404, "lastMs": 165, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 166, "p95ms24h": 237, "samples24h": 68, "samples30d": 68, "days": [ { "date": "2026-11-04", "probes": 68, "ok": 68 } ] }, "vendorStatus": { "page": "https://savvycal.instatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:26:44.192765993Z" }, "securityTxt": { "url": "https://savvycal.com/.well-known/security.txt", "state": "valid", "expires": "2027-05-03T00:00:00.000Z", "checkedAt": "2026-11-04T15:54:05.808454415Z" }, "updatedAt": "2026-11-04T22:02:57.017408527Z" } }, "edges": [ { "by": 59, "category": "schema", "leads": "savvycal", "name": "Schema \u0026 documentation", "reasons": { "a": "Public product and help material earns 15 points for explaining user workflows. No external-agent machine contract, input schemas or API error catalogue was verified. This score concerns integration documentation, not consumer usability.", "b": "OpenAPI 3.0.0 at api.savvycal.com/v1/spec covers all 22 operations with 56 schemas; the MCP tools' schemas could not be read without signing in (23 of 25). llms.txt and a Markdown twin of every docs page (10). Only 8 of the 22 operations carry a description, and those state constraints (events must match an open slot, an invalid filter resets every filter) rather than when to choose another endpoint (10 of 20). Required flags on 14 of 43 parameters, 34 enum properties across the schemas, `limit` bounded 1 to 100, `until` at most 31 days after `from` (12 of 15). Example values on parameters and a documented error shape keyed by field, with 400, 401, 404, 422 and 429 declared per operation, but no full response examples (10 of 15). A /v1 path and a promise that changes are additive, with dated product updates on the feedback board but no API changelog (9 of 15). 23 + 10 + 10 + 12 + 10 + 9 = 74." }, "scores": { "a": 15, "b": 74 } }, { "by": 55, "category": "reliability", "leads": "savvycal", "name": "Reliability", "reasons": { "a": "No readable 90-day incident record established (5). The consumer or commercially available product is documented (10). No public external-agent rate limits, safe-retry contract or SLA were verified (0).", "b": "Read with the hosted lines. Instatus page at savvycal.instatus.com with App, Microsoft 365, Google Calendar and Integrations components and a month-by-month history (20). No notices from June to November 2026 and 100 per cent App uptime each month, a clean record (30). The only limit with a number is in the OpenAPI spec, 10 event creations a minute per link, failed ones included; nothing covers the rest of the API (7 of 15). That 429 is declared with no Retry-After, backoff guidance or idempotency key, and webhooks are the only place retries are described (3 of 15). No SLA; the terms give the service as is (0). The v1 API is generally available and the MCP server, announced 27 October 2026, is not marked beta (10). 20 + 30 + 7 + 3 + 0 + 10 = 70." }, "scores": { "a": 15, "b": 70 } }, { "by": 43, "category": "ergonomics", "leads": "savvycal", "name": "Agent ergonomics", "reasons": { "a": "Documented user workflows and handoff controls earn 10 points. External-agent output controls, batching and safe write retries were not verified. Do not infer a callable API from the product's own AI functions.", "b": "List responses are sized by `limit` (default 20, at most 100) with no field selection. The MCP server lists 63 tools with no documented toolset or read-only list, though a client can ask for the `mcp:read` scope alone (10 of 25). Cursor pagination with `after`, `before` and `limit`, and date and status filters on events (17 of 20). Errors name the field, the failed validation and a limit count, which an agent can act on, but a 429 carries no wait time (14 of 20). No idempotency key on booking or link creation, and the MCP annotations could not be read; the docs say the assistant confirms before cancelling, deleting or inviting (6 of 20). Creating an event needs five fields, and there is no official SDK in any language (6 of 15). 10 + 17 + 14 + 6 + 6 = 53." }, "scores": { "a": 10, "b": 53 } }, { "by": 40, "category": "security", "leads": "savvycal", "name": "Security \u0026 auth", "reasons": { "a": "Published account, privacy and user-control documentation earns 10 points. No external-agent credential scopes, per-call audit contract or complete least-privilege API were verified. Vendor security statements were not independently audited.", "b": "OAuth 2 authorisation code apps with 2-hour access tokens and refresh tokens, and personal access tokens, both in the Authorization header only. The spec declares no scopes for either, and PAT expiry and revocation are not described. The MCP server uses OAuth 2.1 with PKCE S256, dynamic client registration, `mcp:read` and `mcp:write` scopes and a revocation endpoint (22 of 30). `mcp:read` gives a read-only MCP grant, and the vendor says the assistant asks before booking, cancelling, deleting or inviting. REST tokens have no read-only form (14 of 20). Invitee names, answers and metadata written by outsiders come back through events and webhooks with no injection guidance; the AI page says the assistant sees calendar conflicts but not event names (2 of 15). Webhook request logs and a Connected Apps list with revoke, but no per-call audit log for the operator (4 of 15). Valid security.txt to 2 May 2027, a security page and an SSDLC page, but no SOC 2 or ISO 27001 (the page says not yet) and no bug bounty (8 of 20). 22 + 14 + 2 + 4 + 8 = 50." }, "scores": { "a": 10, "b": 50 } }, { "by": 40, "category": "maintenance", "leads": "savvycal", "name": "Maintenance \u0026 community", "reasons": { "a": "No dated service release series, support-response sample, official developer SDK or dependency health evidence established (0). An active website alone is not a release history.", "b": "Read as a closed service. The newest dated change is the MCP integration of 27 October 2026 on the updates board (30). It is the only dated entry since 7 July, so fewer than three in 90 days (0 of 20). A public updates board, a feature request board and a support address with a stated 24-hour reply within US Central business hours (10 of 15). No official SDKs (0). No package to assess (0). 30 + 0 + 10 + 0 + 0 = 40." }, "scores": { "a": 0, "b": 40 } }, { "by": 33, "category": "transparency", "leads": "savvycal", "name": "Transparency \u0026 trust", "reasons": { "a": "Published product, commercial and privacy disclosures earn 35 points. Governing API terms, service-specific retention, deprecation commitments and infrastructure locations were not all established. Where only website terms were found, they are not presented as a partner API agreement.", "b": "Closed service with terms that name SavvyCal, Inc. under Minnesota law and forbid automated access to the site, with the API left to the developer docs (15 of 30). The privacy policy (17 October 2026), DPA (16 January 2023) and processor list (24 October 2026) agree on US hosting, Stripe and return or destruction on termination, but no retention period is stated beyond account lifetime (22 of 30). The developer overview promises additive changes; there is no deprecation policy or dated notice, and the terms allow any feature to change without notice (5 of 20). A processor list with purposes, hosting on Fly.io in Virginia and Crunchy Bridge on AWS us-east, but no locations per processor (15 of 20). 15 + 22 + 5 + 15 = 57." }, "scores": { "a": 40, "b": 73 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Cozi, Inc.", "b": "SavvyCal, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.savvycal.com/v1", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service; see governing terms and the access limitations below.", "b": "none", "name": "Licence" }, { "a": "none", "b": "63", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-27", "name": "Last release" }, { "a": "2026-10-13", "b": "2026-01-21", "name": "Terms last updated" }, { "a": "2026-06-11", "b": "2026-10-17", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "2.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "SavvyCal API + MCP scores 57 (C) on agent readiness against Cozi Family Organizer's 16.1 (F), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Cozi Family Organizer or SavvyCal API + MCP?" }, { "answer": "No hosted endpoint is listed for Cozi Family Organizer. SavvyCal API + MCP has a hosted endpoint at https://api.savvycal.com/v1.", "question": "Can an agent call Cozi Family Organizer and SavvyCal API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Cozi is a shared family calendar, shopping-list and meal-planning app.", "slug": "cozi", "watchFor": "No official external-agent write API verified" }, { "aheadOn": [ "Reliability, 70 against 15", "Schema \u0026 documentation, 74 against 15", "Agent ergonomics, 53 against 10", "Security \u0026 auth, 50 against 10", "Maintenance \u0026 community, 40 against 0", "Transparency \u0026 trust, 73 against 40" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "An agent booking on a person's SavvyCal links or driving their account through the MCP server.", "slug": "savvycal", "watchFor": "No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)" } ], "history": { "cozi": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.4, "from": 15.7, "fromGrade": "F", "to": 16.1, "toGrade": "F" } ], "savvycal": null }, "job": { "capability": "calendar.read", "name": "Calendar access" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cozi.json", "title": "Acuity Scheduling API vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.json", "title": "Acuity Scheduling API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-cozi.json", "title": "Agenda Hero vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.json", "title": "Agenda Hero vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-cozi.json", "title": "Apiroc Unified Calendar API vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/apiroc-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-savvycal.json", "title": "Apiroc Unified Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/apiroc-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cozi.json", "title": "Aurinko Calendar API vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal.json", "title": "Aurinko Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-cozi.json", "title": "Cal.com API v2 + MCP vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/cal-com-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-savvycal.json", "title": "Cal.com API v2 + MCP vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cal-com-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-cozi.json", "title": "Calendly API + MCP vs Cozi Family Organizer", "url": "https://www.anchorterminal.com/compare/calendly-vs-cozi" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-savvycal.json", "title": "Calendly API + MCP vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/calendly-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-cronofy.json", "title": "Cozi Family Organizer vs Cronofy API", "url": "https://www.anchorterminal.com/compare/cozi-vs-cronofy" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-google-calendar-api.json", "title": "Cozi Family Organizer vs Google Calendar API", "url": "https://www.anchorterminal.com/compare/cozi-vs-google-calendar-api" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-microsoft-graph-calendar.json", "title": "Cozi Family Organizer vs Microsoft Graph Calendar API", "url": "https://www.anchorterminal.com/compare/cozi-vs-microsoft-graph-calendar" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar.json", "title": "Cozi Family Organizer vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-zoom-scheduler.json", "title": "Cozi Family Organizer vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/cozi-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-savvycal.json", "title": "Cronofy API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/cronofy-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.json", "title": "Google Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.json", "title": "Microsoft Graph Calendar API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.json", "title": "Nylas Calendar and Scheduler API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.json", "title": "SavvyCal API + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.json", "title": "SavvyCal API + MCP vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler" } ], "panel": null, "scores": [ { "by": 55, "cozi": 15, "edge": "savvycal", "key": "reliability", "name": "Reliability", "savvycal": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 59, "cozi": 15, "edge": "savvycal", "key": "schema", "name": "Schema \u0026 documentation", "savvycal": 74, "weight": 13 }, { "by": 43, "cozi": 10, "edge": "savvycal", "key": "ergonomics", "name": "Agent ergonomics", "savvycal": 53, "weight": 13 }, { "by": 40, "cozi": 10, "edge": "savvycal", "key": "security", "name": "Security \u0026 auth", "savvycal": 50, "weight": 14 }, { "by": 0, "cozi": 30, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "savvycal": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 40, "cozi": 0, "edge": "savvycal", "key": "maintenance", "name": "Maintenance \u0026 community", "savvycal": 40, "weight": 7 }, { "by": 33, "cozi": 40, "edge": "savvycal", "key": "transparency", "name": "Transparency \u0026 trust", "savvycal": 73, "weight": 7 } ], "summary": "SavvyCal API + MCP scores 57 (C) on agent readiness against Cozi Family Organizer's 16.1 (F), and leads in 6 of 7 scored categories. Both do calendar access.", "tasks": null, "tutorials": [], "verdicts": { "cozi": "Documented read-only calendar exchange. No official external-agent write API verified.", "savvycal": "A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cozi-vs-savvycal", "json": "https://www.anchorterminal.com/compare/cozi-vs-savvycal.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cozi-vs-savvycal.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cozi-vs-savvycal.min.md" }, "markdown": "SavvyCal API + MCP scores 57 (C) on agent readiness against Cozi Family Organizer's 16.1 (F), and leads in 6 of 7 scored categories. Both do calendar access.\n\n- Cozi Family Organizer: grade F, 16.1/100, rank #1312 of 1349. Markdown https://www.anchorterminal.com/tools/cozi.md · JSON https://www.anchorterminal.com/api/v1/tools/cozi.json\n- SavvyCal API + MCP: grade C, 57/100, rank #726 of 1349. Markdown https://www.anchorterminal.com/tools/savvycal.md · JSON https://www.anchorterminal.com/api/v1/tools/savvycal.json\n- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md\n- All 89 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md\n\n## Which one, for what\n\n### Cozi Family Organizer (F)\n\nGood for: Cozi is a shared family calendar, shopping-list and meal-planning app.\n\nWatch for: No official external-agent write API verified\n\n### SavvyCal API + MCP (C)\n\nGood for: An agent booking on a person's SavvyCal links or driving their account through the MCP server.\n\nAhead on:\n- Reliability, 70 against 15\n- Schema \u0026 documentation, 74 against 15\n- Agent ergonomics, 53 against 10\n- Security \u0026 auth, 50 against 10\n- Maintenance \u0026 community, 40 against 0\n- Transparency \u0026 trust, 73 against 40\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: No general rate limit documented. The spec names one 429, on creating events (10 a minute per link)\n\n\n## Why the edge\n\n### Schema \u0026 documentation: SavvyCal API + MCP +59\n\n- Cozi Family Organizer (15): Public product and help material earns 15 points for explaining user workflows. No external-agent machine contract, input schemas or API error catalogue was verified. This score concerns integration documentation, not consumer usability.\n- SavvyCal API + MCP (74): OpenAPI 3.0.0 at api.savvycal.com/v1/spec covers all 22 operations with 56 schemas; the MCP tools' schemas could not be read without signing in (23 of 25). llms.txt and a Markdown twin of every docs page (10). Only 8 of the 22 operations carry a description, and those state constraints (events must match an open slot, an invalid filter resets every filter) rather than when to choose another endpoint (10 of 20). Required flags on 14 of 43 parameters, 34 enum properties across the schemas, `limit` bounded 1 to 100, `until` at most 31 days after `from` (12 of 15). Example values on parameters and a documented error shape keyed by field, with 400, 401, 404, 422 and 429 declared per operation, but no full response examples (10 of 15). A /v1 path and a promise that changes are additive, with dated product updates on the feedback board but no API changelog (9 of 15). 23 + 10 + 10 + 12 + 10 + 9 = 74.\n\n### Reliability: SavvyCal API + MCP +55\n\n- Cozi Family Organizer (15): No readable 90-day incident record established (5). The consumer or commercially available product is documented (10). No public external-agent rate limits, safe-retry contract or SLA were verified (0).\n- SavvyCal API + MCP (70): Read with the hosted lines. Instatus page at savvycal.instatus.com with App, Microsoft 365, Google Calendar and Integrations components and a month-by-month history (20). No notices from June to November 2026 and 100 per cent App uptime each month, a clean record (30). The only limit with a number is in the OpenAPI spec, 10 event creations a minute per link, failed ones included; nothing covers the rest of the API (7 of 15). That 429 is declared with no Retry-After, backoff guidance or idempotency key, and webhooks are the only place retries are described (3 of 15). No SLA; the terms give the service as is (0). The v1 API is generally available and the MCP server, announced 27 October 2026, is not marked beta (10). 20 + 30 + 7 + 3 + 0 + 10 = 70.\n\n### Agent ergonomics: SavvyCal API + MCP +43\n\n- Cozi Family Organizer (10): Documented user workflows and handoff controls earn 10 points. External-agent output controls, batching and safe write retries were not verified. Do not infer a callable API from the product's own AI functions.\n- SavvyCal API + MCP (53): List responses are sized by `limit` (default 20, at most 100) with no field selection. The MCP server lists 63 tools with no documented toolset or read-only list, though a client can ask for the `mcp:read` scope alone (10 of 25). Cursor pagination with `after`, `before` and `limit`, and date and status filters on events (17 of 20). Errors name the field, the failed validation and a limit count, which an agent can act on, but a 429 carries no wait time (14 of 20). No idempotency key on booking or link creation, and the MCP annotations could not be read; the docs say the assistant confirms before cancelling, deleting or inviting (6 of 20). Creating an event needs five fields, and there is no official SDK in any language (6 of 15). 10 + 17 + 14 + 6 + 6 = 53.\n\n### Security \u0026 auth: SavvyCal API + MCP +40\n\n- Cozi Family Organizer (10): Published account, privacy and user-control documentation earns 10 points. No external-agent credential scopes, per-call audit contract or complete least-privilege API were verified. Vendor security statements were not independently audited.\n- SavvyCal API + MCP (50): OAuth 2 authorisation code apps with 2-hour access tokens and refresh tokens, and personal access tokens, both in the Authorization header only. The spec declares no scopes for either, and PAT expiry and revocation are not described. The MCP server uses OAuth 2.1 with PKCE S256, dynamic client registration, `mcp:read` and `mcp:write` scopes and a revocation endpoint (22 of 30). `mcp:read` gives a read-only MCP grant, and the vendor says the assistant asks before booking, cancelling, deleting or inviting. REST tokens have no read-only form (14 of 20). Invitee names, answers and metadata written by outsiders come back through events and webhooks with no injection guidance; the AI page says the assistant sees calendar conflicts but not event names (2 of 15). Webhook request logs and a Connected Apps list with revoke, but no per-call audit log for the operator (4 of 15). Valid security.txt to 2 May 2027, a security page and an SSDLC page, but no SOC 2 or ISO 27001 (the page says not yet) and no bug bounty (8 of 20). 22 + 14 + 2 + 4 + 8 = 50.\n\n### Maintenance \u0026 community: SavvyCal API + MCP +40\n\n- Cozi Family Organizer (0): No dated service release series, support-response sample, official developer SDK or dependency health evidence established (0). An active website alone is not a release history.\n- SavvyCal API + MCP (40): Read as a closed service. The newest dated change is the MCP integration of 27 October 2026 on the updates board (30). It is the only dated entry since 7 July, so fewer than three in 90 days (0 of 20). A public updates board, a feature request board and a support address with a stated 24-hour reply within US Central business hours (10 of 15). No official SDKs (0). No package to assess (0). 30 + 0 + 10 + 0 + 0 = 40.\n\n### Transparency \u0026 trust: SavvyCal API + MCP +33\n\n- Cozi Family Organizer (40): Published product, commercial and privacy disclosures earn 35 points. Governing API terms, service-specific retention, deprecation commitments and infrastructure locations were not all established. Where only website terms were found, they are not presented as a partner API agreement.\n- SavvyCal API + MCP (73): Closed service with terms that name SavvyCal, Inc. under Minnesota law and forbid automated access to the site, with the API left to the developer docs (15 of 30). The privacy policy (17 October 2026), DPA (16 January 2023) and processor list (24 October 2026) agree on US hosting, Stripe and return or destruction on termination, but no retention period is stated beyond account lifetime (22 of 30). The developer overview promises additive changes; there is no deprecation policy or dated notice, and the terms allow any feature to change without notice (5 of 20). A processor list with purposes, hosting on Fly.io in Virginia and Crunchy Bridge on AWS us-east, but no locations per processor (15 of 20). 15 + 22 + 5 + 15 = 57.\n\n## Score by category\n\n| Category | Weight | Cozi Family Organizer | SavvyCal API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 70 | SavvyCal API + MCP +55 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 15 | 74 | SavvyCal API + MCP +59 |\n| Agent ergonomics | 13% (16.2 this run) | 10 | 53 | SavvyCal API + MCP +43 |\n| Security \u0026 auth | 14% (17.5 this run) | 10 | 50 | SavvyCal API + MCP +40 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 0 | 40 | SavvyCal API + MCP +40 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 40 | 73 | SavvyCal API + MCP +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **16.1 · F** | **57 · C** | |\n\n## Facts side by side\n\n| Fact | Cozi Family Organizer | SavvyCal API + MCP |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Cozi, Inc. | SavvyCal, Inc. |\n| Hosted endpoint | no (local only) | `https://api.savvycal.com/v1` |\n| Transports | | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service; see governing terms and the access limitations below. | none |\n| Tools exposed | none | 63 |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-27 |\n| Terms last updated | 2026-10-13 | 2026-01-21 |\n| Privacy policy last updated | 2026-06-11 | 2026-10-17 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Agent reviews | 2.3/5 (4) | none |\n\n## How the scores have moved\n\n### Cozi Family Organizer\n\n- +0.4 on 27 October 2026: checklist\n\n### SavvyCal API + MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Cozi Family Organizer.** Documented read-only calendar exchange. No official external-agent write API verified.\n\n**SavvyCal API + MCP.** A small REST API with a public OpenAPI spec, cursor pagination and signed webhooks, plus a hosted MCP server with 63 tools, OAuth 2.1 and read and write scopes, on every plan. No general rate limit, idempotency key, SDK or certification was found, and booking through a link needs a paid seat.\n\n## Before you call either\n\n### Cozi Family Organizer\n\n1. Use official read-only feeds for calendar visibility.\n2. Make edits in the originating calendar and allow for the refresh delay.\n\n### SavvyCal API + MCP\n\n1. Call GET /v1/links/{link_id}/slots with `from` and `until` (at most 31 days apart) and book only a returned slot; POST /v1/links/{link_id}/events refuses other times with 422\n2. Keep event creation under 10 requests a minute per link, failed attempts included, or expect 429 with no Retry-After\n3. Page with the `after` and `before` cursors from `metadata` and `limit` up to 100; an invalid filter value resets every filter to its default\n4. Connect the MCP server with a client that supports dynamic client registration, and request `mcp:read` when the task only reads\n5. Verify webhooks with HMAC-SHA256 over the raw body against `x-savvycal-signature` and answer 2xx quickly\n\n## Questions\n\n### Which is better for AI agents, Cozi Family Organizer or SavvyCal API + MCP?\n\nSavvyCal API + MCP scores 57 (C) on agent readiness against Cozi Family Organizer's 16.1 (F), and leads in 6 of 7 scored categories.\n\n### Can an agent call Cozi Family Organizer and SavvyCal API + MCP without installing anything?\n\nNo hosted endpoint is listed for Cozi Family Organizer. SavvyCal API + MCP has a hosted endpoint at https://api.savvycal.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cozi-vs-savvycal.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cozi-vs-savvycal.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cozi\", \"b\": \"savvycal\"}`. From a terminal: `anchor compare cozi savvycal`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cozi.json and https://www.anchorterminal.com/api/v1/tools/savvycal.json\n\n## Other comparisons with Cozi Family Organizer or SavvyCal API + MCP\n\n- [Acuity Scheduling API vs Cozi Family Organizer](https://www.anchorterminal.com/compare/acuity-scheduling-vs-cozi.md)\n- [Acuity Scheduling API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/acuity-scheduling-vs-savvycal.md)\n- [Agenda Hero vs Cozi Family Organizer](https://www.anchorterminal.com/compare/agenda-hero-vs-cozi.md)\n- [Agenda Hero vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/agenda-hero-vs-savvycal.md)\n- [Apiroc Unified Calendar API vs Cozi Family Organizer](https://www.anchorterminal.com/compare/apiroc-vs-cozi.md)\n- [Apiroc Unified Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/apiroc-vs-savvycal.md)\n- [Aurinko Calendar API vs Cozi Family Organizer](https://www.anchorterminal.com/compare/aurinko-calendar-vs-cozi.md)\n- [Aurinko Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/aurinko-calendar-vs-savvycal.md)\n- [Cal.com API v2 + MCP vs Cozi Family Organizer](https://www.anchorterminal.com/compare/cal-com-vs-cozi.md)\n- [Cal.com API v2 + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cal-com-vs-savvycal.md)\n- [Calendly API + MCP vs Cozi Family Organizer](https://www.anchorterminal.com/compare/calendly-vs-cozi.md)\n- [Calendly API + MCP vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/calendly-vs-savvycal.md)\n- [Cozi Family Organizer vs Cronofy API](https://www.anchorterminal.com/compare/cozi-vs-cronofy.md)\n- [Cozi Family Organizer vs Google Calendar API](https://www.anchorterminal.com/compare/cozi-vs-google-calendar-api.md)\n- [Cozi Family Organizer vs Microsoft Graph Calendar API](https://www.anchorterminal.com/compare/cozi-vs-microsoft-graph-calendar.md)\n- [Cozi Family Organizer vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar.md)\n- [Cozi Family Organizer vs Zoom Scheduler API](https://www.anchorterminal.com/compare/cozi-vs-zoom-scheduler.md)\n- [Cronofy API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/cronofy-vs-savvycal.md)\n- [Google Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/google-calendar-api-vs-savvycal.md)\n- [Microsoft Graph Calendar API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-savvycal.md)\n- [Nylas Calendar and Scheduler API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.md)\n- [SavvyCal API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.md)\n- [SavvyCal API + MCP vs Zoom Scheduler API](https://www.anchorterminal.com/compare/savvycal-vs-zoom-scheduler.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Cozi Family Organizer vs SavvyCal API + MCP", "url": "" } ], "description": "SavvyCal scores 57 (C) to Cozi Family Organizer's 16.1 (F) for calendar access. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cozi Family Organizer F 16.1", "SavvyCal API + MCP C 57", "scores" ], "h1": "Cozi Family Organizer vs SavvyCal API + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cozi-vs-savvycal", "published": "2026-10-01", "section": "tools", "title": "Cozi Family Organizer vs SavvyCal for AI agents (2026)", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/cozi-vs-savvycal" }, "tokens": { "markdown": 4000, "slim": 2280 }, "version": 1 }