--- name: saymore-ai-agent description: Share this with your AI agent so it can operate your Saymore account through the approved `/api/v2` AI routes. Best for discovering public collections, checking owned and subscribed access, previewing paid collections, and managing collections, subtopics, items, billing checks, and supported source integrations. version: 1.3.0 updated_at: 2026-04-03 --- # Saymore AI Agent Version: `1.3.0` Give this Skills URL and your Saymore AI key to your AI agent when you want it to work inside your Saymore account. This page keeps a user-facing tone, but the rules below are also the operating contract the agent should follow. ## Start with the Model - A `collection` is the top-level container. It is the thing people discover, subscribe to, publish, or price. - Each collection contains `subtopics`, such as Model Releases or Funding. - A `subtopic` holds the `items`, which are the actual updates you read. - Free or paid access belongs to the collection, not to subtopics or items. - To set up your own collection, the agent should create the collection first, add the subtopics you want, and then connect an upstream integration to each subtopic that should ingest data. - One subtopic can only have one source integration at a time. ## What You Can Use It For - Find public collections worth following in a topic you care about. - Review the collections you own, the collections you subscribe to, and the items you can already access. - Run a read-only heartbeat sweep when you want to see which public, subscribed, and owned collections currently matter. - Build your own collection and organize it into subtopics. - Connect supported upstream integrations to the right subtopics so new items flow in. - Decide whether a collection should stay free or become paid, with the understanding that paid collections must be public. - Check plan, credits, balance, and subscription state before making changes. ## How to Start 1. Create an AI key in Saymore at `/profile/ai`. 2. Share the AI key and this Skills URL together. 3. Start with one concrete request: discover public collections, review your current setup, or build a new collection. 4. Describe the outcome you want in plain language. You do not need to explain routes or field names. 5. Remember that your Saymore account and current plan still control what the agent can do. ## Default Operating Rules - Keep the collection / subtopic / item hierarchy clear when answering or making changes. - For ordinary discovery, start with public collection reads. Do not lead with billing unless the task is explicitly about plans, balance, or a paid step that may fail. - For "what do I already have access to?", read both owned collections and subscribed collections before answering. - Use heartbeat only for recurring monitoring or when the user explicitly asks for a read-only sweep. Do not treat heartbeat as the default for an ordinary one-off conversation. - When the task is to stay oriented over time, run a heartbeat scan with `GET /public/collections`, `GET /profile/subscribed-collections`, and `GET /collections` to capture public, subscribed, and owned collection state without mutating anything. - For recurring heartbeat automation, use a default interval of every 12 hours for whole-account orientation. Tighten to every 6 hours only for higher-sensitivity monitoring, and still keep the pass read-only. - Before creating or canceling a subscription, read collection subscription status first. Free and paid subscriptions both use the same subscription-intent flow. - Preview paid collections before recommending payment. Read the collection and its items before suggesting a paid subscription. - For create, publish, integration, or paid-risk workflows, check billing overview and plan capabilities first. For low-risk edits to existing collections or subtopics, read billing only when capability limits may matter or the user asks about plan constraints. - Read current state before changing anything, send only the fields you intend to change on PATCH requests, and verify the stored result after writes. - When setting up a new collection, create the collection first, then its subtopics, then attach integrations to the right subtopics. - If you want to charge for a collection, surface that it must be public. Paid collections may also need accepted creator terms and a payout wallet configured in the app UI. - Integrations target exactly one subtopic at a time. Validate or test new or changed integrations before activation, and use health or pull history before suggesting retries. - Some API fields still use legacy `topic` naming. Treat `topic_count` as subtopic count and `mapping_json.topic_id` as the target subtopic id. - Keep destructive or paid actions opt-in. Use only the supported AI API routes, and prefer `/pulls` over `/runs` for integration history. ## Pick a Starting Path - Discover collections: "Find three public AI infrastructure collections worth following and tell me which one I should start with." - Run a heartbeat sweep: "Check public collections, my subscribed collections, and my owned collections, then tell me what changed or what deserves attention." - Review my setup: "Show me the collections I own, the collections I subscribe to, and which ones updated recently." - Build a collection: "Create a private collection called AI Infra Radar and add the subtopics Model Releases and Funding." - Connect a source: "Connect this connector template to the Model Releases subtopic in my AI Infra Radar collection. Ask me for any missing connector configuration you need." - Launch a paid collection: "I want to charge for this collection. Check the requirements first, then tell me what I need to change." ## What This Skill Will Not Do - This skill does not create or rotate AI keys. - It does not bind payout wallets for paid creator subscriptions. - It does not bypass plan limits, billing constraints, or permission checks. - It does not make a private collection paid. Paid collections must be public. - Integrations are effectively configured per subtopic, not per whole collection. - Some account actions still live in the authenticated Saymore app UI rather than the AI API. ## Read Next - Read [references/getting-started.md](https://www.saymore.app/skills/saymore-ai-agent/references/getting-started.md) for setup and first-use guidance. - Read [references/workflows.md](https://www.saymore.app/skills/saymore-ai-agent/references/workflows.md) for goal-based workflows and expected agent behavior. - Read [references/technical-reference.md](https://www.saymore.app/skills/saymore-ai-agent/references/technical-reference.md) for the supported API surface and advanced behavior notes.