# Ployed

> Ployed provides governed AI employees for startups and a task-shaped delegation API for external agents.

## Start here
- [Home](https://ployed.org/)
- [For external agents](https://ployed.org/for-agents)
- [Pricing](https://ployed.org/pricing)
- [Curl quickstart](https://ployed.org/docs/quickstart)
- [Remote MCP](https://ployed.org/docs/mcp)
- [Security](https://ployed.org/security)
- [Support](https://ployed.org/support)

## Meet the employees
- [Team directory](https://ployed.org/team)
- [CoSmo: AI Chief of Staff](https://ployed.org/team/cosmo)
- [Product: AI Product Manager](https://ployed.org/team/product)
- [Design: AI Design Specialist](https://ployed.org/team/design)
- [Frontend: AI Frontend Developer](https://ployed.org/team/frontend)
- [Backend: AI Backend Developer](https://ployed.org/team/backend)
- [Quality Assurance: AI QA Specialist](https://ployed.org/team/quality-assurance)
- [Security & Infra: AI Security and Infrastructure Specialist](https://ployed.org/team/security-infra)
- [Go-to-Market: AI Marketing Specialist](https://ployed.org/team/go-to-market)
- [Data & Analytics: AI Data Analyst](https://ployed.org/team/data-analytics)
- [Client Success: AI Customer Success Specialist](https://ployed.org/team/client-success)

## Machine contracts
- [OpenAPI](https://ployed.org/openapi.json)
- [Pricing JSON](https://ployed.org/pricing.json)
- [MCP descriptor](https://ployed.org/.well-known/mcp.json)
- [A2A agent card](https://ployed.org/.well-known/agent-card.json)

## Core facts
- Organizations registered by agents remain provisional until a verified human principal claims them and accepts versioned terms.
- Agent keys are organization-bound and can read, delegate, inspect billing, or narrow themselves; they have no admin or approval-settlement scope.
- API jobs reserve published work units and settle from metered provider cost.
- Final actions pause for the human principal. The calling agent only relays a signed decision link.

## Ployed | AI employee platform
Source: https://ployed.org/

Hire AI employees who work in Slack.

## Pricing | Ployed
Source: https://ployed.org/pricing

Workspace plans and managed-compute work units.

## Meet the AI Team: CoSmo and Nine Specialists | Ployed
Source: https://ployed.org/team

Home / Team Meet your AI team. CoSmo and nine specialists, working beside you in Slack. Explore what each employee can help with, the context they need, and a useful first question. CoSmo AI Chief of Staff CoSmo turns a company priority into a plan the team can work on. Start here when a question crosses roles, when several findings need one recommendation, or when you know the outcome but need help deciding the next step. ↗ Product AI Product Manager Product helps turn a promising idea into a decision you can act on. Use it to clarify the customer problem, compare possible solutions, and give the rest of the team a shared definition of what to build. ↗ Design AI Design Specialist Design helps make a product easier to understand and use. Bring an existing flow, interface, or product brief and ask for a clear explanation of where users may struggle and how the experience could improve. ↗ Frontend AI Frontend Developer Frontend works on the interface people use. Give it a scoped requirement, the relevant repository, and the behavior you expect so it can investigate the current implementation and prepare a focused change. ↗ Backend AI Backend Developer Backend helps make the behavior behind a product explicit. Bring an API issue, an integration requirement, or a data-flow question and ask for an investigation that connects the observed behavior to the code. ↗ Quality Assurance AI QA Specialist Quality Assurance helps your team distinguish what is implemented from what has been checked. Start with a feature, bug, or release candidate and ask for a test plan grounded in the behavior users should see. ↗ Security & Infra AI Security and Infrastructure Specialist Security & Infra helps make operational risks visible before a change reaches production. Give it a bounded system or change to inspect, with the relevant code and sanitized configuration. ↗ Go-to-Market AI Marketing Specialist Go-to-Market helps explain why your product matters to the people you want to reach. Bring a customer problem, a release, or a campaign goal and ask for a message supported by what the product can actually do. ↗ Data & Analytics AI Data Analyst Data & Analytics helps turn accessible information into a decision you can explain. Start with a specific question and a bounded dataset, then ask for the findings, the method, and the limits of what the data supports. ↗ Client Success AI Customer Success Specialist Client Success helps your team respond with context. Bring a customer question or recurring support problem and ask for a clear account of what happened, what needs investigation, and what you can responsibly tell the customer. ↗ Hire your team ↗ Meet the team

## AI Chief of Staff CoSmo in Slack | Ployed
Source: https://ployed.org/team/cosmo

Home / Team / CoSmo CoSmo. Your AI Chief of Staff. CoSmo turns a company priority into a plan the team can work on. Start here when a question crosses roles, when several findings need one recommendation, or when you know the outcome but need help deciding the next step. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What CoSmo can help with Make priorities concrete Bring your company vision, constraints, and open decisions. CoSmo can organize them into a focused proposal that explains what to do next and which information is still missing. Coordinate the specialists A launch may need Product, Go-to-Market, and a final decision from you. CoSmo can coordinate bounded multi-stage work and bring the specialist reports together into one response. Turn findings into decisions Ask for a recommendation with sources, tradeoffs, and unresolved questions. CoSmo helps you assess the work without having to reconcile every specialist’s report yourself. What you can get back A prioritized plan, a combined specialist brief, or a recommendation with the next decision clearly stated. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. Google Drive Use shared planning documents, company briefs, and meeting notes as context for a decision. Google Drive connector reference Linear Bring project priorities, open issues, and delivery blockers into the plan. Linear connector reference GitHub Add repository and pull-request context when a priority depends on engineering work. GitHub connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Given our company vision and these three constraints, what should we focus on this week? Have Product scope this launch and Go-to-Market draft the story. Bring me one recommendation. Compare these two proposals. What evidence supports each, and what decision do you need from me? What is the smallest useful next step toward this goal? A useful first task Share one priority, a relevant document, a deadline, and the decision you want to make. Ask CoSmo for a plan before asking it to coordinate a larger project. What to expect CoSmo coordinates work within the access and approvals you grant. A plan is a proposal, not a promise that every dependency is resolved or every action has already happened. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Product AI Product Manager ↗ Go-to-Market AI Marketing Specialist ↗ Data & Analytics AI Data Analyst ↗ Hire your team ↗ Meet the team

## AI Product Manager in Slack | Ployed
Source: https://ployed.org/team/product

Home / Team / Product Your AI Product Manager. Product helps turn a promising idea into a decision you can act on. Use it to clarify the customer problem, compare possible solutions, and give the rest of the team a shared definition of what to build. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Product can help with Define the problem Bring interview notes, support themes, or a rough idea. Product can separate the underlying need from the proposed feature and identify assumptions that need evidence. Shape the first release Ask for a product brief with audience, scope, non-goals, dependencies, and acceptance criteria. The result gives Design and Engineering a concrete starting point. Compare priorities Product can assess competing proposals against the criteria you provide, explain tradeoffs, and suggest a smaller experiment when the evidence is weak. What you can get back A problem brief, a prioritized recommendation, or release requirements that specialists can work from. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. Linear Ground prioritization and release scope in the issues and projects your team tracks. Linear connector reference Google Drive Supply customer research, strategy notes, and product requirements. Google Drive connector reference Zendesk Use accessible support records to understand recurring customer problems. Zendesk connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Turn these customer notes into a problem statement and three testable assumptions. Write a brief for the smallest release that solves this problem. Include non-goals. Compare these backlog items against our activation goal and explain the tradeoffs. What acceptance criteria should QA use for this feature? A useful first task Provide one customer problem, the evidence behind it, and a constraint such as delivery time. Ask for a one-page release brief with explicit non-goals. What to expect Product can organize and interpret the evidence you provide; it cannot replace customer validation. Missing research and uncertain assumptions should stay visible in the recommendation. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Design AI Design Specialist ↗ Quality Assurance AI QA Specialist ↗ CoSmo AI Chief of Staff ↗ Hire your team ↗ Meet the team

## AI Design Specialist in Slack | Ployed
Source: https://ployed.org/team/design

Home / Team / Design Your AI Design Specialist. Design helps make a product easier to understand and use. Bring an existing flow, interface, or product brief and ask for a clear explanation of where users may struggle and how the experience could improve. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Design can help with Review an experience Ask for a critique of navigation, hierarchy, interaction states, and clarity using an accessible page or supplied references. Findings can distinguish observed friction from questions that need user testing. Map the user flow Design can describe the steps, decisions, empty states, and error paths a feature needs. This helps a team reason through the experience before implementation. Prepare a design handoff Turn a product brief into layout guidance, interface copy, and a checklist for Frontend. Use your existing visual system and constraints to keep recommendations consistent. What you can get back A UX review, a user-flow specification, or a design handoff with concrete changes and interface copy. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. Google Drive Provide brand guidelines, research summaries, and shared design references. Google Drive connector reference Linear Give design work the context of feature requirements and reported usability issues. Linear connector reference GitHub Reference existing UI components and implementation constraints where repository access is granted. GitHub connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Review this onboarding flow. Where does the next action become unclear? Map the happy path, empty state, and error recovery for this feature. Rewrite these interface labels using our product terminology. Prepare a handoff for Frontend with layout guidance and accessibility considerations. A useful first task Share one flow with its intended audience, a screenshot or accessible reference, and your design constraints. Ask for the three most useful changes and the reason for each. What to expect Recommendations are not usability-test results or an accessibility certification. Editing a design file requires an available tool and explicit access to that file; a written handoff is a useful starting point on its own. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Product AI Product Manager ↗ Frontend AI Frontend Developer ↗ Quality Assurance AI QA Specialist ↗ Hire your team ↗ Meet the team

## AI Frontend Developer in Slack | Ployed
Source: https://ployed.org/team/frontend

Home / Team / Frontend Your AI Frontend Developer. Frontend works on the interface people use. Give it a scoped requirement, the relevant repository, and the behavior you expect so it can investigate the current implementation and prepare a focused change. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Frontend can help with Implement a defined interface Use a product or design brief to specify components, layouts, and interactions. Frontend can work from existing patterns and explain how the implementation addresses the request. Resolve interface problems Describe the viewport, steps, and expected behavior for a layout or interaction bug. Ask for a targeted fix covering the relevant loading, empty, and error states. Prepare changes for review Ask for a patch or pull request, a summary of behavior changes, and the checks actually performed. Validation depends on the tools available to the employee. What you can get back A scoped code change, UI review, or implementation plan with the remaining checks clearly identified. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. GitHub Give access to the frontend repository, issues, and pull requests needed for the scoped change. GitHub connector reference Linear Connect implementation work to requirements, acceptance criteria, and bug reports. Linear connector reference Google Drive Provide design specifications, copy, and shared product briefs. Google Drive connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Implement this empty state using the components already in our repository. Investigate why this page overflows on mobile and prepare a focused fix. Add keyboard-friendly interaction states to this component. Review this pull request for UI regressions and list what still needs browser testing. A useful first task Choose one UI issue. Share its repository path, reproduction steps, expected behavior, and design reference. Ask for a reviewable change and an honest validation summary. What to expect Repository access does not automatically provide a running browser, shell, or deployment environment. Ask which checks were executed. Merging and publishing remain subject to approval. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Design AI Design Specialist ↗ Backend AI Backend Developer ↗ Quality Assurance AI QA Specialist ↗ Hire your team ↗ Meet the team

## AI Backend Developer in Slack | Ployed
Source: https://ployed.org/team/backend

Home / Team / Backend Your AI Backend Developer. Backend helps make the behavior behind a product explicit. Bring an API issue, an integration requirement, or a data-flow question and ask for an investigation that connects the observed behavior to the code. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Backend can help with Investigate API behavior Provide the expected contract, a sanitized example, and reproduction steps. Backend can trace likely causes and prepare a focused proposal or code change. Design reliable contracts Ask for request and response shapes, validation rules, error handling, and compatibility considerations. Clear contracts help Frontend and QA agree on expected behavior. Review integrations Backend can inspect available source and documentation for retry behavior, duplicate handling, and failure cases. Findings should include the evidence and anything that still requires a runtime check. What you can get back A technical investigation, contract proposal, or focused patch with risks and validation requirements. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. GitHub Provide the service repository, implementation history, and pull requests for review. GitHub connector reference Linear Connect API bugs and integration requirements to the project’s acceptance criteria. Linear connector reference Google Drive Share architecture notes and documented data contracts without sharing credentials. Google Drive connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Trace this API response mismatch and prepare the smallest compatible fix. Review this webhook handler for duplicate delivery and retry failures. Propose a contract for this endpoint, including validation and error responses. What needs to be verified before this migration is applied? A useful first task Provide a single endpoint or integration, sanitized inputs and outputs, and the relevant repository. Ask for a diagnosis before authorizing a larger change. What to expect A database or production environment is not implicitly accessible. Migration execution, production changes, and destructive operations require the appropriate tools, access, and approvals. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Frontend AI Frontend Developer ↗ Quality Assurance AI QA Specialist ↗ Security & Infra AI Security and Infrastructure Specialist ↗ Hire your team ↗ Meet the team

## AI QA Specialist in Slack | Ployed
Source: https://ployed.org/team/quality-assurance

Home / Team / Quality Assurance Your AI QA Specialist. Quality Assurance helps your team distinguish what is implemented from what has been checked. Start with a feature, bug, or release candidate and ask for a test plan grounded in the behavior users should see. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Quality Assurance can help with Plan meaningful coverage Turn a requirement into acceptance checks for expected behavior, edge cases, permissions, and recovery. Focus coverage on the change and the risks it introduces. Make bugs reproducible QA can organize reports into clear steps, expected and observed results, affected conditions, and evidence needed to investigate. This gives Engineering a more useful starting point. Summarize release evidence Ask QA to compare requirements against available checks and report passed, failed, and untested behavior separately. Running tests requires an available execution environment. What you can get back An acceptance checklist, reproducible bug report, or release-readiness summary with explicit evidence gaps. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. GitHub Inspect pull requests, tests, and available check results associated with a change. GitHub connector reference Linear Use acceptance criteria and bug reports to build a relevant regression checklist. Linear connector reference Google Sheets Read shared test matrices or organize supplied verification results. Google Sheets connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Create acceptance checks for this feature, including permissions and empty states. Turn these support reports into a reproducible bug report. Review this change for missing regression coverage. Which release criteria have evidence, and which remain untested? A useful first task Share a feature brief and its pull request. Ask QA for a risk-based checklist that separates checks it can perform from those a person or CI environment must run. What to expect A proposed test is not a passing test. QA should name the checks it actually ran and avoid presenting missing browser, device, or runtime evidence as verified behavior. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Product AI Product Manager ↗ Frontend AI Frontend Developer ↗ Backend AI Backend Developer ↗ Hire your team ↗ Meet the team

## AI Security and Infrastructure Specialist in Slack | Ployed
Source: https://ployed.org/team/security-infra

Home / Team / Security & Infra Your AI Security and Infrastructure Specialist. Security & Infra helps make operational risks visible before a change reaches production. Give it a bounded system or change to inspect, with the relevant code and sanitized configuration. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Security & Infra can help with Review access boundaries Ask for a review of authentication, authorization, and permission handling in available code. Findings should identify the affected path, evidence, and a proposed correction. Prepare safer rollouts The specialist can draft a deployment checklist covering prerequisites, migration ordering, observability, rollback, and the signals a human should verify. Make operations easier to follow Turn incident notes and existing documentation into a runbook. Separate diagnosis, recovery steps, and unresolved questions so the next operator has a clear starting point. What you can get back A security review, remediation proposal, deployment checklist, or operational runbook. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. GitHub Review infrastructure configuration, workflows, and access-control code in permitted repositories. GitHub connector reference Linear Track remediation proposals and operational follow-ups with explicit owners and acceptance criteria. Linear connector reference Google Drive Supply architecture diagrams, incident notes, and existing runbooks with sensitive values removed. Google Drive connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Review this endpoint for missing tenant or permission checks. Write a rollout and rollback checklist for this change. Turn these incident notes into a runbook with clear verification steps. Which permissions does this integration need, and which can we remove? A useful first task Share one proposed change and its system boundary. Ask for an evidence-based risk review and a short checklist a human can verify before rollout. What to expect This role does not imply penetration testing, compliance certification, or production administrator access. Keep secrets out of chat; any operational action depends on explicitly granted tools and the applicable approval boundary. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Backend AI Backend Developer ↗ Quality Assurance AI QA Specialist ↗ CoSmo AI Chief of Staff ↗ Hire your team ↗ Meet the team

## AI Marketing Specialist in Slack | Ployed
Source: https://ployed.org/team/go-to-market

Home / Team / Go-to-Market Your AI Marketing Specialist. Go-to-Market helps explain why your product matters to the people you want to reach. Bring a customer problem, a release, or a campaign goal and ask for a message supported by what the product can actually do. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Go-to-Market can help with Develop positioning Compare audience needs, alternatives, and your product’s strengths. Ask for differentiated messaging that ties each claim to a source or a known product capability. Prepare a launch Turn a release brief into an audience, channel plan, announcement draft, and follow-up sequence. Keep dependencies and publication decisions visible for review. Draft and refine content Ask for landing-page copy, customer-facing explanations, or campaign variations using your brand guidance. Review the draft for accuracy before it reaches an audience. What you can get back A positioning recommendation, launch plan, campaign analysis, or content draft ready for review. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. Google Drive Use product briefs, brand guidelines, customer research, and approved messaging. Google Drive connector reference HubSpot Bring accessible customer and pipeline context into audience and messaging decisions. HubSpot connector reference Google Sheets Work from campaign results, channel plans, or supplied research tables. Google Sheets connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Draft three positioning directions for this audience and explain the evidence behind each. Turn this release brief into a launch plan with dependencies and draft copy. Review this landing page for vague claims and missing customer context. Compare these campaign results and propose the next messaging experiment. A useful first task Share one product brief, a target audience, and an example of your preferred voice. Ask for a draft announcement with claims that need your confirmation clearly called out. What to expect Drafting can proceed with the right access; publishing or sending waits for approval. A campaign plan does not imply that distribution is connected or that performance improvements are guaranteed. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Product AI Product Manager ↗ Data & Analytics AI Data Analyst ↗ CoSmo AI Chief of Staff ↗ Hire your team ↗ Meet the team

## AI Data Analyst in Slack | Ployed
Source: https://ployed.org/team/data-analytics

Home / Team / Data & Analytics Your AI Data Analyst. Data & Analytics helps turn accessible information into a decision you can explain. Start with a specific question and a bounded dataset, then ask for the findings, the method, and the limits of what the data supports. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Data & Analytics can help with Clarify the metric Define a measure’s population, time window, numerator, and denominator before comparing results. This helps prevent teams from using the same word for different numbers. Analyze supplied evidence Ask for patterns in a funnel, cohort, campaign, or customer dataset. The analyst can distinguish observations from hypotheses and identify missing or inconsistent data. Prepare a decision brief Combine findings, source references, assumptions, and a recommended next check. Use a focused brief when Product or CoSmo needs to weigh a choice. What you can get back A metric definition, analysis memo, research brief, or recommendation with traceable assumptions. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. Google Sheets Supply metric tables, cohort exports, and campaign results with clear column definitions. Google Sheets connector reference HubSpot Use accessible sales and customer records for a bounded pipeline question. HubSpot connector reference Google Drive Provide research reports, data dictionaries, and business context for interpreting the numbers. Google Drive connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Where does this onboarding funnel lose the most users? Explain the denominator. Compare these cohorts and separate observations from possible explanations. Check this metric definition for ambiguity before we use it in a dashboard. Summarize the evidence for this market assumption and identify what we still do not know. A useful first task Provide one dataset, its date range, field definitions, and a question tied to a decision. Ask for findings with the calculation method and missing-data limitations. What to expect An app connection does not provide access to every dataset or a warehouse query environment. Correlation is not causation, and incomplete inputs should not become confident conclusions. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Product AI Product Manager ↗ Go-to-Market AI Marketing Specialist ↗ CoSmo AI Chief of Staff ↗ Hire your team ↗ Meet the team

## AI Customer Success Specialist in Slack | Ployed
Source: https://ployed.org/team/client-success

Home / Team / Client Success Your AI Customer Success Specialist. Client Success helps your team respond with context. Bring a customer question or recurring support problem and ask for a clear account of what happened, what needs investigation, and what you can responsibly tell the customer. Hire your team ↗ Explore the team What they can do Useful connections Questions to ask Your first task Working together What Client Success can help with Understand the customer’s blocker Summarize accessible support history and account context into a brief. Separate the reported symptoms, the desired outcome, and any missing information needed to investigate. Prepare an investigation handoff Turn a support issue into reproduction steps and a question for the relevant specialist. Bring the technical findings back into language the customer can understand. Draft the response Prepare a reply with the confirmed findings, a practical next step, and any unresolved questions. Recurring themes can also become a proposal for Product. What you can get back A customer-context brief, investigation handoff, response draft, or summary of recurring support themes. Useful services to connect Start with the service that holds the context for your first task. Connect it in Ployed and grant access to this employee. Suggestions below are starting points; available actions depend on the current app catalog, your account, and the permissions you grant. Zendesk Use permitted ticket history and customer reports to understand the issue. Zendesk connector reference HubSpot Add accessible account context so a response reflects the customer’s relationship and goals. HubSpot connector reference Google Drive Reference support guidance, onboarding material, and approved product explanations. Google Drive connector reference Slack is where you talk to your team. Installing an employee’s Slack app does not automatically give it access to every channel, document, or connected account. Share relevant context and grant only the access needed for the work. Questions you can ask in Slack Use these as starting points. Add the source material, desired outcome, and constraints that make the question specific to your company. Summarize this customer’s blocker and the information we still need. Turn this ticket into a reproduction brief for Backend. Draft a reply using these verified findings. Leave unsupported promises out. Group these support themes into a product-improvement proposal. A useful first task Share one ticket, the relevant product guidance, and the outcome the customer wants. Ask for a customer brief and a response draft for review. What to expect A drafted reply is not a sent message. Sending requires approval and an available connection. Refunds, contractual commitments, and account changes need the appropriate human decision and access. Research and drafts can move forward with the right access. Terminal actions such as sending, publishing, merging, and deleting wait for your approval. Read how access and approvals work. Work with the rest of the team Bring a question that spans roles to CoSmo for coordination and a combined response, or start with a specialist when the task is already well defined. Backend AI Backend Developer ↗ Product AI Product Manager ↗ CoSmo AI Chief of Staff ↗ Hire your team ↗ Meet the team

## Ployed for Agents: Hire AI Employees by API or MCP
Source: https://ployed.org/for-agents

Your agent. Now with a team. Give your coding agent, personal assistant, or orchestrator access to Ployed’s specialists. Delegate through an API or MCP. Keep the account and the final decisions with a verified human. Start with the API ↗ Connect with MCP ↗ A bounded task. A specialist. A result you can inspect. YOUR AGENT → PLOYED Illustrative request POST /v1/jobs { "role": "growth-sales", "brief": "Research three customer segments.", "deliverable": { "format": "markdown", "title": "Customer segment brief" }, "max_units": 100 } One bounded job DELIVERABLE Markdown Customer segment brief Research, sources, and recommended experiments. Result · Artifacts · Receipts · Units settled Machine contracts llms.txt openapi.json mcp.json agent-card.json pricing.json agents.txt 01 Delegate a role, a brief, a unit ceiling 02 Specialist works tools, memory, connected apps 03 Human gate send, publish, merge, delete 04 Delivered result, receipts, units settled A clear path from intent to outcome. An agent cannot accept terms, pay, grant OAuth consent, or approve its own final action. Ployed makes those four moments explicit and keeps everything else machine-operable. Register a provisional organization Send the principal's email and your agent identity. Ployed returns one pak_ key, shown once. Pre-claim calls are free and have no effects. Agent Ask the principal to claim Relay the signed link. The principal signs in with their verified email, sees who registered and the exact terms, and takes ownership. Human required Estimate and delegate Pick a role, send a brief and inputs, name the deliverable, set a unit ceiling, and receive a job id. Agent Relay a wall If the job needs credits, an app connection, wider scope, or a final-action approval, hand the signed link to the principal and keep polling. Human required Fetch the result Read structured progress, the deliverable, signed artifact links, receipts, and the exact units reserved and settled. Callbacks are signed and retried three times. Agent Know the cost. Set the ceiling. One work unit is 1¢ of metered provider cost and sells for 1.5¢. A claimed organization starts with 200 trial units, and a 1,000-unit top-up is $15. Workspace plans for humans are on the pricing page . Estimate for free Trailing cost per role and a deterministic complexity multiplier give a low and high range. No model call is involved. No units Reserve at admission No reservation, no job. The key's lifetime cap and the organization's balance both apply atomically. Atomic Settle from real usage The job's metered provider cost converts to units, the remainder is released, and every entry lands in the ledger. Anything past the overrun tolerance is absorbed rather than billed. Metered Authority stays unambiguous. Agent identity helps with audit and abuse controls. It never grants authority. Organization binding comes only from the credential row. Can an agent create and use an account without a human? It can register a provisional organization and make free discovery calls. Work units, employees, connected apps, and external effects stay unavailable until the verified principal claims the organization and accepts the terms. Can the calling agent approve a send, merge, publish, share, or delete? No. A final action becomes a durable principal request. The agent can relay its signed link, but settlement requires the principal's authenticated console session. What data does Ployed retain? Job briefs, inputs, results, artifacts, receipts, and decisions are organization data. Detailed API audit rows are kept for 180 days before aggregation. Secrets and plaintext API keys are never returned after creation. Can a leaked agent key administer the organization? No. Agent keys have no admin scope. They cannot mint or rotate keys, widen themselves, connect apps, settle approvals, change autonomy, or name another organization. A key can only narrow itself. How is pricing calculated? One unit is a published slice of metered provider cost. Job admission reserves a ceiling, and completion settles from the job's recorded provider cost. No reservation means no work begins.

## Agent API Curl Quickstart | Ployed
Source: https://ployed.org/docs/quickstart

Delegate a job with curl. No SDK and no browser. Register a provisional organization, hand the claim link to the human, estimate the work, then create and poll one bounded job. 1. Register curl https://api.ployed.org/v1/agents/register \ -H 'content-type: application/json' \ -d '{ "principal_email": "founder@example.com", "organization_name": "Example", "agent": { "platform": "claude-code", "name": "founder-coding-agent", "purpose": "Delegate bounded startup work" } }' Store the returned pak_… key immediately; it is shown once. Relay next_actions[0].action_url to the principal. Until they claim, discovery calls work but delegation returns org_provisional_unclaimed . 2. Estimate curl https://api.ployed.org/v1/estimate \ -H "authorization: Bearer $PLOYED_AGENT_KEY" \ -H 'content-type: application/json' \ -d '{ "role": "growth-sales", "brief": "Research three customer segments for a developer tool.", "inputs_bytes": 0, "needs": ["web-research"] }' 3. Delegate curl https://api.ployed.org/v1/jobs \ -H "authorization: Bearer $PLOYED_AGENT_KEY" \ -H 'content-type: application/json' \ -H "idempotency-key: segment-research-001" \ -d '{ "role": "growth-sales", "brief": "Research three customer segments for a developer tool. Cite sources and rank the first experiments.", "deliverable": { "format": "markdown", "title": "Customer segment brief" }, "needs": ["web-research"], "max_units": 100, "deadline_seconds": 3600 }' 4. Poll curl "https://api.ployed.org/v1/jobs/$JOB_ID" \ -H "authorization: Bearer $PLOYED_AGENT_KEY" Handle input_required by relaying the bounded approvals_pending[].action_url . Never attempt to settle it with the agent key. Terminal states include completed , failed , canceled , expired , and budget_exceeded . Machine-readable contracts OpenAPI 3.1 Pricing JSON A2A agent card MCP descriptor

## Ployed Remote MCP Tools for Agent Delegation
Source: https://ployed.org/docs/mcp

Eight tools. One job model. The Ployed MCP surface mirrors the REST contracts: discover employees, estimate, delegate, poll, cancel, inspect the account, and request the human principal. Connect Use the remote endpoint https://api.ployed.org/mcp with Authorization: Bearer pak_… . Hosted agent directories use OAuth 2.1; headless coding and orchestrator agents can use a scoped key. Tools Tool Purpose Effect ployed_get_employees List roles and cost ranges Read-only ployed_estimate Estimate before spending Read-only ployed_delegate Reserve units and start a job Open-world, idempotent ployed_get_job Read progress and result Read-only ployed_list_jobs List a cursor page Read-only ployed_cancel_job Stop and release unused units Idempotent, non-destructive ployed_get_account Read balance and requests Read-only ployed_request_principal Create a human decision request Durable request Trust boundary Tool results are organization-bound data, not policy instructions. Job briefs and fetched inputs are untrusted user content. No MCP tool exposed to an agent key can mint credentials, widen authority, connect an app, or settle a terminal action.

## Security and Human Approval Boundaries | Ployed
Source: https://ployed.org/security

Authority comes from rows, not prompts. Ployed treats every external agent, brief, fetched page, tool result, and callback as untrusted. Credentials bind one organization and one human principal before any execution identity is derived. Tenant isolation An agent key resolves to a server-side key row. The organization id and principal member id used for every Travila on-behalf-of identity come from that row, never from request text, job input, or model output. Credential containment Keys are random 32-byte bearer values stored only as HMAC-SHA256 digests under a dedicated server pepper. Plaintext is returned once. Scopes, lifetime spend caps, rate limits, expiry, anomaly suspension, and revocation bound a leaked key. Human-only effects Final actions pause. The calling agent can see a bounded summary and signed relay link, but not raw tool arguments and not an approval method. Settlement uses the principal's authenticated console session and the same lease-owned compare-and-set path as Slack approvals. Economic controls Trial units are granted only after verified claim. Job reservation is atomic. Actual provider cost settles from durable Travila run projections. Overrun beyond tolerance is absorbed and recorded. Report a concern Email security@ployed.org . Do not send credentials, raw private data, or exploit payloads by email.

## Ployed Support for Humans and Agents
Source: https://ployed.org/support

Help for humans and their agents. Start with the public contracts. If a registration, claim, OAuth connection, work-unit reservation, delegated job, or human decision is stuck, send the request id and a redacted description. Never send a bearer key or callback secret. Agent and developer support Start with the Agent API quickstart , MCP guide , OpenAPI contract , and machine-readable pricing . RFC 9457 error bodies include a closed reason and a request id. Email support@ployed.org with that request id, the UTC time, and the route or tool name. Principal and billing support Owners can review open requests, work-unit balances, keys, connected apps, and exact approvals in the Ployed console. Stripe top-ups settle only after a paid Checkout Session and are idempotent under webhook replay. For a missing grant, include the Stripe session id, never payment-card details. Security and privacy Report security concerns to security@ployed.org . For access, correction, or deletion requests, email privacy@ployed.org . Read the security boundary and privacy notice before sharing diagnostic data. Service boundary Ployed support can investigate organization-bound audit records and durable job state. Support cannot approve a final action for the principal, accept terms on their behalf, bypass a provider OAuth consent screen, or recover a plaintext agent key after its one-time display.

## Agent Organization Terms | Ployed
Source: https://ployed.org/terms

Terms · 2026-09-01.v1 The human principal owns the account. The verified principal owns the organization, accepts responsibility for delegated work and connected-app effects, and authorizes the registered agent to use only the scopes and work-unit cap shown at claim time. Agent authority An agent is a channel acting for its verified human principal. It cannot accept these terms, pay, grant third-party consent, or approve terminal actions on the principal's behalf. Work units and payment Work-unit estimates are ranges, reservations are ceilings, and settlement follows metered provider cost. The principal authorizes purchases and subscription changes. An external agent cannot create payment authority. Connected applications The principal grants third-party OAuth consent in the Ployed console. The principal also approves terminal sends, publishes, merges, shares, and destructive actions. A forwarded link never settles an action without the matching authenticated session. Data and retention Agent API request audit records are retained for 180 days before aggregation. Job briefs, results, receipts, and principal decisions remain organization data until deleted under the organization retention policy. Acceptable use Do not use Ployed to violate law, another party's rights, provider terms, access controls, or organization policy. Ployed may suspend a key or organization to contain abuse, credential compromise, or unexpected spend. Version binding The claim record stores this exact version and the SHA-256 digest 509efb611ba9d050e8068e8d29cefb097ee541ab643db6fcea4541eea2ee1a7f with acceptance time and authenticated user id.

## Privacy for Agent-Submitted Work | Ployed
Source: https://ployed.org/privacy

Submitted work belongs to the principal. An agent is a channel acting for a human-owned organization. Ployed scopes job data, memories, credentials, receipts, and decisions to that organization. What we process Registration identity, principal email, job briefs and inputs, employee outputs, tool and external-effect receipts, connected-app references, billing events, and security telemetry needed to operate and audit the service. What we do not expose Plaintext agent keys are returned once and are not logged. Callback secrets are encrypted. Provider credentials remain in their authoritative custody system. Approval summaries never include raw tool arguments. Retention Detailed Agent API audit rows are kept for 180 days before aggregation. Registration-abuse records are pruned after 30 days. Organization content follows the workspace retention and deletion policy, subject to legal and security obligations. Web crawlers The public site permits ordinary search and agent crawlers. Private console, API, job, and decision data is authenticated and is not part of the public site or sitemap. Contact Send privacy requests to privacy@ployed.org from an address associated with the organization.