# Gusto > Gusto Embedded Payroll is a REST API for running US payroll inside another product, covering company and worker onboarding, payroll calculation and submission, tax filing and contractor payments. Production access needs a partnership with Gusto. A demo environment is self-serve. - Canonical: https://www.anchorterminal.com/tools/gusto - Markdown: https://www.anchorterminal.com/tools/gusto.md (~7,550 tokens) - Slim: https://www.anchorterminal.com/tools/gusto.min.md (~1,930 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/gusto.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade B · 63.3/100 · rank #283 of 629 · #3 in Payroll infrastructure · not agent-ready · confidence medium** ## Assessment This listing covers the Embedded Payroll API. Every reference page carries an OpenAPI 3.1 definition, payroll is calculated as a preview before submission, and each API version gets 12 months of deprecation support. Production needs commercial and security approval, no price was readable, and the status page lists 11 incidents between 14 July and 5 October 2026, five marked major. ## Facts | Field | Value | | --- | --- | | Vendor | Gusto, Inc. (https://gusto.com) | | Kind | HTTP API | | Category | Payroll infrastructure (https://www.anchorterminal.com/categories/payroll) | | Transport | HTTP | | Auth | OAuth · Graded on the Embedded Payroll API, which needs a partnership. A developer signs up at dev.gusto.com, creates an organisation and an application, and gets a client ID and secret for the demo environment. POST /oauth/token with `grant_type` system_access returns a two-hour system token for partner-level calls, and creating a partner-managed company returns an access and refresh token pair for that company alone. Scopes are assigned by Gusto, and production keys follow commercial, security and implementation reviews. Access to an existing employer's Gusto account is separate. Partner apps use the App Integrations API with the OAuth 2.0 authorisation code grant after Production Pre-Approval and a security review. A customer's own company is reached through the Gusto CLI or the Gusto MCP server, which sign in by OAuth with dynamic client registration and PKCE. | | Pricing | Paid (Paid) · No price could be read. gusto.com and embedded.gusto.com answered our reader with a bot check, and the developer docs carry no figures. The introduction says commercial conversations are required before production, and an invoices endpoint returns the active companies used to calculate a partner's invoice. The demo environment is open to any developer with a Developer Portal account, with generated demo companies and no contract (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the developer docs, the API reference or the llms.txt index (checked 2026-10-08). | | Licence | Proprietary service under Gusto's API Policy and Developer Terms of Service. The API clients on GitHub are MIT, and the React SDK and the Gusto CLI are Apache-2.0 | | Packages | npm: `@gusto/embedded-api`; npm: `@gusto/embedded-react-sdk`; pypi: `gusto-embedded` | | Source | https://github.com/Gusto/gusto-typescript-client | | Docs | https://docs.gusto.com/embedded-payroll/docs/introduction | | llms.txt | https://docs.gusto.com/llms.txt | | Last release | 2026-10-01 | | GitHub stars | 2 (as of 2026-10-08) | | npm downloads / week | 24,731 | | Surface graded | Embedded Payroll API (REST, JSON), demo at https://api.gusto-demo.com and production at https://api.gusto.com, all paths under /v1. 317 reference pages in the embedded project | | Payroll coverage | Regular and off-cycle payrolls, prepare, calculate, submit and cancel, payroll receipts, pay schedules, contractor payments, tax payments, time off policies, benefits, garnishments, forms and reports | | Other Gusto surfaces | App Integrations API for partner apps on an existing Gusto account (update a payroll, no run). Gusto CLI and Gusto MCP server for a customer's own company (draft payroll, no submit). Dev Assistant MCP for documentation search, in beta | | Credentials | System access token from client ID and secret (`grant_type` system_access) for partner-level calls. One access and refresh token pair per company. Access tokens last two hours. Scopes named resource:action, such as `payrolls:run`, assigned by Gusto before production | | Access steps | Developer Portal account, organisation and application are self-serve for the demo. Production keys follow commercial, security and implementation reviews with the partnerships team | | Rate limits | 200 requests a minute per application and user, rolling 60-second window, 429 with `Retry-After`, `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` | | Pagination and sorting | `page` and `per` (25 by default, 100 at most on payrolls) with `X-Total-Count` and `X-Total-Pages` headers. Cursor pagination with `starting_after_uuid` and `limit` on some endpoints. `sort_by` with an allowlist per endpoint | | Writes | PUT takes a delta plus the resource's `version` and returns 409 on a stale one. `idempotency_key` on People Batch creation. Calculate and submit answer 202 and are polled | | Errors | JSON `errors` array with `error_key`, `category`, `message` and `metadata`. 18 documented categories, among them `payroll_blocker`, `invalid_resource_version`, `missing_oauth_scopes` and `rate_limit_exceeded` | | Versioning | Dated versions in `X-Gusto-API-Version`, about one a quarter. Six months of full support and six of limited support after deprecation, then 406. `Deprecation`, `Sunset` and `Link` headers | | Webhooks | Subscriptions verified with a `verification_token`, up to 16 retries over three days, and GET /v1/events with 30 days of events | | SDKs | API clients for TypeScript (@gusto/embedded-api 0.16.2, 1 October 2026), Python, Java, C# and Ruby, generated by Speakeasy, MIT, all labelled beta. React SDK @gusto/embedded-react-sdk 0.56.5 (7 October 2026), Apache-2.0 | | Status | https://gustoapi.statuspage.io for the Embedded API (APIs, Webhooks, Embedded Flows, Developer Portal and three portals). https://status.gusto.com for the Gusto product | | Capabilities | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors, hr.onboarding, hr.time-off | | Tags | hosted, payroll, oauth, partner-approval, sandbox, llms-txt, webhooks, typescript, python, java, csharp, ruby, mcp, cli, status-page | | JSON | https://www.anchorterminal.com/api/v1/tools/gusto.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 58 | 11.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 86 | 14.0 | | Agent ergonomics | 13% | 16.2 | 82 | 13.3 | | Security & auth | 14% | 17.5 | 60 | 10.5 | | Payments & pricing | 10% | 12.5 | 15 | 1.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 76 | 6.7 | | Transparency & trust (editorial 44, provenance 77) | 7% | 8.8 | 61 | 5.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **63.3 → B** | ### Why each score - Reliability 58: Read with the hosted lines and scored on the Embedded Payroll API. https://gustoapi.statuspage.io is a status page for the Embedded API with seven components and incident history (20). It lists 11 incidents between 14 July and 5 October 2026, five marked major. One on 28 September is titled a complete outage for APIs, with a fix about 29 minutes after it opened. All calls to the payroll update endpoint returned 500 on 14 July (about 80 minutes to recovery), a single-payroll GET returned 500 on 27 July (about 97 minutes to the fix), payroll retrieval and preparation failed on 29 July (about 88 minutes), and webhooks and payroll endpoints had a partial outage on 5 October (an hour to the fix). That is several majors on the core payroll endpoints (0). 200 requests a minute per application and user, rolling window (15). 429 with `Retry-After` and three `X-RateLimit` headers, a `version` check on every PUT, and an idempotency key found on People Batch only (13 of 15). The API Policy says Gusto makes no representations about uptime, and no SLA was found (0). v2026-06-15 is marked stable (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 86: Each of 317 reference pages serves an OpenAPI 3.1 definition for its operation as Markdown. The whole specification sits in a repository that asked for credentials, so there is no single public file (20 of 25). llms.txt for the site and per project, and every guide has a Markdown twin (10). Operation descriptions state what happens, the scope needed and when to poll, and guides walk through payroll step by step. Few say when not to use an endpoint (15 of 20). Enums on status, type and include parameters, formats and patterns on fields such as `ssn`, and required fields listed. Dates are plain strings (13 of 15). Curl examples in guides, example error bodies per category and per endpoint. One guide's JavaScript sample uses older parameters than its curl sample (13 of 15). Dated versions, a version upgrade guide with breaking changes by version, and a changelog (15). - Agent ergonomics 82: `include` chooses which parts of a payroll come back, and `page` and `per` size lists. No field selection (18 of 25). Page and cursor pagination with total headers, date and status filters, and `sort_by` with a per-endpoint allowlist (20). Errors carry `error_key`, `category` and `metadata`, with 18 documented categories and a list of payroll blockers. Messages are display text and may change (18 of 20). A `version` on every PUT with 409 on conflict, delta updates, and 202 with polling on calculate and submit. Idempotency keys were found on one endpoint, and this is an HTTP API with no MCP annotations to read (14 of 20). Five official API clients (TypeScript, Python, Java, C#, Ruby), all labelled beta, and payroll setup needs many calls before a first run (12 of 15). - Security & auth 60: OAuth-style tokens with resource:action scopes. A system token comes from the client ID and secret, each company has its own access and refresh pair, access tokens last two hours and refresh tokens rotate on use. Secrets travel in the body or the `Authorization` header. Scopes are assigned by Gusto per application, not chosen per token (27 of 30). Read and write scopes are separate and `payrolls:run` is its own scope. Calculate gives a preview and the docs recommend a review screen, but nothing in the API holds a submission for approval. A payroll can be cancelled until 3:30pm PST on its deadline (13 of 20). The API docs say free-text values are content and must not drive logic. Guidance on treating returned text as untrusted appears only in the Gusto CLI's README, a different surface (6 of 15). GET /v1/events returns 30 days of events, the Developer Portal shows webhook activity, and responses carry `x-request-id`. No per-call log was found (8 of 15). The CLI's SECURITY.md gives security@gusto.com with a two-business-day acknowledgement, and partners pass a security review. Gusto's own security page and security.txt couldn't be read, so certifications and any bounty are unconfirmed (6 of 20). - Payments & pricing 15: Read with the hosted rubric. No x402, MPP or L402 (0). No price could be read. The pricing pages answered with a bot check and the docs have no figures, only a statement that commercial conversations come before production (0). The demo environment is open to any developer account with generated demo companies and no contract, and no card is mentioned. It is a sandbox, not a production tier (15 of 20). A person signs up in the Developer Portal and production keys follow reviews (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 76: The changelog's latest entry is dated 1 October 2026, the TypeScript client 0.16.2 shipped the same day and the React SDK 0.56.5 on 7 October (30). Changelog entries on 3 August, 1 September and 1 October plus four feature entries between them, and three TypeScript client versions since 31 August (20). Closed service with a changelog, developer@gusto.com, named Technical Solutions contacts for partners and GitHub issues on the client repositories, which we couldn't read (10 of 15). The TypeScript client is current. `gusto-embedded` on PyPI stopped at 0.2.4 on 16 April 2025 though its repository has newer versioned packages, and every client is beta (10 of 15). Clients are generated by Speakeasy with generation and publish workflows. No test results are visible (6 of 10). - Transparency & trust 61: Closed service. The API Policy is published in the docs and dated 11 July 2022. The Developer Terms of Service couldn't be read. API clients are MIT, the React SDK and CLI Apache-2.0 (15 of 30). The API Policy says Gusto may monitor use and keep aggregate data, and the events endpoint keeps 30 days. The privacy policy and any DPA couldn't be read, and the docs state no retention periods for payroll data (6 of 30). Each version gets six months of full and six of limited support after deprecation, with dates in a table and `Deprecation` and `Sunset` headers (20). No sub-processor list or data locations in the docs. The product status page names AWS and Cloudflare as providers (3 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/gusto.md (JSON https://www.anchorterminal.com/fixes/gusto.json) ### What we couldn't check - unchecked: gusto.com and embedded.gusto.com answered our reader with a bot check, so pricing, the Developer Terms of Service, the privacy policy, any DPA or sub-processor list, the security page and /.well-known/security.txt weren't read - unchecked: the product pages for the Gusto MCP server and Gusto CLI on gusto.com, so which plans include them and any cost are unconfirmed - unchecked: the MCP server's tool list and annotations. tools/list at https://mcp.api.gusto.com returned 401 without a token - unchecked: weekly downloads of gusto-embedded on PyPI. pypistats.org answered 429 three times - unchecked: open issues and replies on the client repositories, which aren't in a git clone - Whether a partner contract includes an SLA. The public API Policy makes no uptime commitment - Whether idempotency keys are accepted on POST endpoints beyond People Batch. The fundamentals page describes them for creates without naming a header - The full OpenAPI file is fetched from Gusto/Gusto-Partner-API with a token in the client workflow, and that repository asked us for credentials - Incident durations are taken from update timestamps on the status page, which gives the time to a fix and not a measured outage length - The star count is for Gusto/gusto-typescript-client. Gusto's main API has no single public repository ### Sources - documentation index for both projects: (seen 2026-10-08) - introduction and production review requirement: (seen 2026-10-08) - quickstart, organisation, application and first calls: (seen 2026-10-08) - system and company access tokens: (seen 2026-10-08) - pagination, sorting, idempotency, versions, rate limits and scopes: (seen 2026-10-08) - API versioning and deprecation timeline: (seen 2026-10-08) - version statuses and breaking changes by version: (seen 2026-10-08) - breaking change policy: (seen 2026-10-08) - error shapes and categories: (seen 2026-10-08) - regular payroll steps: (seen 2026-10-08) - submit payroll reference with OpenAPI 3.1 definition: (seen 2026-10-08) - list payrolls reference, parameters and enums: (seen 2026-10-08) - invoices endpoint: (seen 2026-10-08) - events endpoint, 30 days: (seen 2026-10-08) - webhooks, verification and retries: (seen 2026-10-08) - API clients and their beta status: (seen 2026-10-08) - Dev Assistant MCP: (seen 2026-10-08) - API Policy: (seen 2026-10-08) - changelog: (seen 2026-10-08) - App Integrations introduction and Production Pre-Approval: (seen 2026-10-08) - App Integrations compared with Gusto Embedded: (seen 2026-10-08) - App Integrations security review: (seen 2026-10-08) - Embedded API status incidents: (seen 2026-10-08) - Gusto product status incidents: (seen 2026-10-08) - TypeScript API client repository, tags and Speakeasy workflow: (seen 2026-10-08) - React SDK repository and tags: (seen 2026-10-08) - Gusto CLI repository, README, AGENTS.md and SECURITY.md: (seen 2026-10-08) - MCP server OAuth metadata: (seen 2026-10-08) - TypeScript client on npm: (seen 2026-10-08) - Python client on PyPI: (seen 2026-10-08) - official MCP registry search, no entries: (seen 2026-10-08) - unauthenticated call to the demo API (401 and headers): (seen 2026-10-08) ## Who's behind it (provenance 77/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Gusto, Inc. | 20/20 | | Domain age | gusto.com, registered 1995-08-23 (31 years) | 15/15 | | Endpoint on the vendor's domain | gusto.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | not found | 0/10 | | Status page | gustoapi.statuspage.io | 10/10 | | Changelog | published | 10/10 | | security.txt | could not be fetched | 0/10 | The NOTICE file in Gusto/gusto-cli reads Copyright 2026 Gusto, Inc. Production calls go to https://api.gusto.com. The demo environment is on a separate domain, api.gusto-demo.com. The terms URL is the one named in the OpenAPI definitions on the reference pages. gusto.com answered our reader with a bot check, so the terms, the privacy policy and /.well-known/security.txt weren't read. The API Policy published in the docs is dated 11 July 2022 and refers to Gusto's Privacy Policy without a readable link. RDAP for gusto.com gives a registration date of 1995-08-23. The docs embed https://gustoapi.statuspage.io as the API status page. status.gusto.com covers the Gusto product and also lists an API component. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://gusto.com/about/terms/developer-terms-of-service), read 2026-10-08. Our reader couldn't read it (the page answered HTTP 403 to our reader). **Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0. ## Live (updated 2026-10-08 17:24 UTC) - Vendor status page: none, All Systems Operational - github `Gusto/gusto-typescript-client` gusto_embedded_v_2025_11_15/v0.3.2, released 2026-10-01 - npm `@gusto/embedded-api` 0.16.2 - npm `@gusto/embedded-react-sdk` 0.56.5 - pypi `gusto-embedded` 0.2.4, released 2025-04-16 - security.txt: unknown - Always current: https://www.anchorterminal.com/api/v1/live/gusto.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Each of 317 reference pages serves an OpenAPI 3.1 definition as Markdown, and llms.txt indexes both documentation projects - Payroll runs in steps (prepare, calculate, submit). Calculate returns a preview with `submission_blockers` before any money moves - Each API version gets 12 months of phased support after deprecation, with dates published and `Deprecation`, `Sunset` and `Link` response headers - Company access tokens work for one company only, expire after two hours and rotate the refresh token on use - Rate limit of 200 requests a minute per application and user, with `Retry-After` and `X-RateLimit-*` headers on responses ## Weaknesses - Production keys need commercial, security and implementation reviews with Gusto's partnerships team, and the docs say not all use cases are supported - The Embedded API status page lists 11 incidents between 14 July and 5 October 2026, five marked major, one titled a complete outage - No price was readable. gusto.com and embedded.gusto.com answered our reader with a bot check, and the docs carry no figures - Idempotency keys were found only on the People Batch endpoint. Other POST calls rely on the caller not repeating them - The five API clients are labelled beta, and the README warns of breaking changes without notice ## Before you call it (notes for agents) 1. Develop against https://api.gusto-demo.com. Production at https://api.gusto.com needs keys Gusto issues after its reviews 2. Send `X-Gusto-API-Version: 2026-06-15` on every call. Without it the application's minimum version applies 3. Send the resource's current `version` with every PUT, and only the fields to change. A stale version returns 409 4. Calculate and submit return 202. Poll GET on the payroll until `calculated_at` is set or the status is processed, and read `submission_blockers` first 5. For a company already on Gusto, the Embedded API is the wrong route. Use the Gusto CLI or the MCP server at https://mcp.api.gusto.com, which draft payroll but can't submit it ## Connect Install: ```bash npm add @gusto/embedded-api ``` First request: ```bash curl --location --request POST 'https://api.gusto-demo.com/oauth/token' \ --header 'Content-Type: application/json' \ --data-raw '{ "client_id": "{{client_id}}", "client_secret": "{{client_secret}}", "grant_type": "system_access" }' ``` Through letme (picks today, calling later): https://letme.dev/gusto. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Zeal | E | 45.4 | 569 | payroll.run, payroll.embedded, payroll.employees, payroll.contractors, payroll.tax-filing, hr.onboarding | no | https://www.anchorterminal.com/tools/zeal.md | | Check | B | 67.5 | 193 | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/check-payroll.md | | Salsa | D | 46.1 | 565 | payroll.run, payroll.embedded, payroll.employees, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/salsa.md | | Finch | BB | 71.6 | 99 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/finch.md | | Deel | B | 69.1 | 158 | hr.time-off, hr.onboarding | no | https://www.anchorterminal.com/tools/deel.md | | BambooHR | C | 61.7 | 319 | hr.time-off, hr.onboarding | no | https://www.anchorterminal.com/tools/bamboohr.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The docs state that commercial, security and implementation reviews are required before partners move to production, and ask developers to contact the partnerships team before building (source: ) - Payroll is prepared, calculated and submitted in separate calls. Calculate and submit are asynchronous and answer 202, and a submitted payroll can be cancelled until 3:30pm PST on the payroll deadline (source: ) - API versions are dated and sent in `X-Gusto-API-Version`. v2026-06-15 is stable, v2026-02-01 reaches limited support on 15 November 2026 and v2025-06-15 is removed on 17 November 2026 (source: ) - The App Integrations API reaches an existing Gusto customer's account by OAuth 2.0, can update a payroll but not run it, and issues production keys only after Production Pre-Approval and a security review (source: ) - Gusto customers connecting their own company are sent to the Gusto CLI and the Gusto MCP server. The CLI is Apache-2.0, at v0.4.0 since 29 September 2026, blocks agent-driven writes until `--confirm`, and has no command to run payroll (source: ) - The MCP server at https://mcp.api.gusto.com publishes OAuth metadata with dynamic client registration, PKCE and 36 scopes. Its tool list needs a token (source: ) - The Dev Assistant MCP at https://embedded-payroll.readme.io/mcp searches the documentation and API reference for coding tools. It is in beta and doesn't act on payroll data (source: ) ## Compare - [Check vs Gusto](https://www.anchorterminal.com/compare/check-payroll-vs-gusto.md): B 67.5 vs B 63.3 - [Gusto vs Salsa](https://www.anchorterminal.com/compare/gusto-vs-salsa.md): B 63.3 vs D 46.1 - [Gusto vs Zeal](https://www.anchorterminal.com/compare/gusto-vs-zeal.md): B 63.3 vs E 45.4 - [Finch vs Gusto](https://www.anchorterminal.com/compare/finch-vs-gusto.md): BB 71.6 vs B 63.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on gusto.com or one of its subdomains, or the README of github.com/Gusto/gusto-typescript-client. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "gusto", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Gusto on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Gusto on Anchor Terminal](https://www.anchorterminal.com/badges/gusto.svg)](https://www.anchorterminal.com/tools/gusto) ``` Plain link: ```html Gusto on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Gusto is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/gusto-dark.png - Light: https://www.anchorterminal.com/assets/share/gusto-light.png