# Fonoa > Fonoa is a hosted indirect tax platform for VAT, GST and sales tax. Its REST API validates tax identification numbers, calculates tax on a transaction and reports e-invoices to tax authorities, with a sandbox and a demo environment. - Canonical: https://www.anchorterminal.com/tools/fonoa - Markdown: https://www.anchorterminal.com/tools/fonoa.md (~7,200 tokens) - Slim: https://www.anchorterminal.com/tools/fonoa.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/fonoa.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 D · 51.7/100 · rank #575 of 722 · #8 in Tax calculation & compliance · not agent-ready · confidence medium** ## Assessment The API reference is served as Markdown with an OpenAPI definition on each endpoint page, and e-invoicing submissions are idempotent by `transaction_id`. API keys are issued by Fonoa staff after contact, no price, rate limit or changelog is published, and the only public terms date from May 2020 and cover older seller sites. ## Facts | Field | Value | | --- | --- | | Vendor | Fonoa Technologies Limited (https://www.fonoa.com) | | Kind | HTTP API | | Category | Tax calculation & compliance (https://www.anchorterminal.com/categories/tax) | | Transport | HTTP | | Endpoint | `https://api.fonoa.com` | | Auth | API key · Every request needs a subscription key in the `Ocp-Apim-Subscription-Key` header. Fonoa issues a primary and a secondary key once a client is onboarded, on request by email or through the sales form, with separate keys for the sandbox and production. No self-serve key page, scopes, read-only keys or expiry were found in the docs. Countries are enabled per tenant, and a call for a country that is not enabled returns `COUNTRIES_NOT_ALLOWED`. Webhooks are set up by asking a Fonoa contact. | | Pricing | Paid (Paid) · No public prices. www.fonoa.com/pricing returns 404 and the site's buttons read "Get in touch". No free tier or self-serve trial was found. The sandbox has unlimited usage with fixed data and the demo environment has limited usage, and a key for either comes from Fonoa after contact (https://docs.fonoa.com/reference/environments, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI definitions or the website (checked 2026-10-08). | | Licence | Proprietary service. The API contract is not published. The public Terms of Service took effect on 14 May 2020 and name older seller sites | | Docs | https://docs.fonoa.com | | llms.txt | https://docs.fonoa.com/llms.txt | | Last release | 2026-10-02 | | API | REST with JSON at https://api.fonoa.com. More than 35 operation pages across Lookup (v1 and v2), Instant Lookup, Tax and E-invoicing, each with an OpenAPI 3.0 definition inline. No single spec file was found | | Tax ID validation | POST `/lookup/v2/single-validations` or `/lookup/v2/batch-validations`, then GET the result or wait for a webhook. `/lookup/v2/single-searches` finds a business by name. `/instant-lookup/v1/find` answers at once for business tax IDs in the countries where it is rolled out | | Calculation | POST `/tax/v2/calculations` with supplier, customer and items returns net, gross and a tax breakdown per item. GET `/tax/v2/calculations/` reads it back and POST `/tax/v2/calculations//commit` marks it committed for revenue tracking | | E-invoicing | POST `/v1/transactions` reports a transaction to a tax authority, with separate endpoints for adjustment, credit and cancellation, a history endpoint per transaction, company onboarding under `/onboarding/v2/companies` and PDF document templates | | Credentials | Subscription key in the `Ocp-Apim-Subscription-Key` header, primary and secondary, issued by Fonoa. Separate sandbox and production keys. No scopes found | | Environments | Sandbox at https://sandbox.fonoa.com (fixed data, unlimited usage), demo at https://api-demo.fonoa.com (limited usage), production at https://api.fonoa.com | | Rate limits | No numbers found. E-invoicing and onboarding endpoints document a 429 that reads "Too many requests were sent for a short period of time. Try again a bit later." | | Errors | 400 responses list errors with `code`, `message` and `type`, such as `field_not_valid` and `unsupported_field`. Later failures arrive on the transaction and by webhook. A missing key returns 401 with the plain text "Unauthorized" | | Paging | Cursor paging on list endpoints with `limit` (default 25) and `next_cursor`. The transaction list takes 27 query parameters and the company list 14 | | Webhooks | One payload shape for all products with `event_type`, `resource_url` and `webhook_id`. A `Fonoa-Webhook-Token` header holds an OIDC token verifiable at https://fit-passport.fonoa.com. Retries use exponential backoff. Configured by Fonoa staff on request | | Pricing | Not published. Contact sales | | SDKs | No official SDK found. An npm search for fonoa returned nothing, PyPI has no `fonoa` project and GitHub has no fonoa organisation | | Certifications | ISO/IEC 27001 badge on the security page. Fonoa says penetration test reports can be shared under NDA. The Vanta trust centre at trust.fonoa.com is drawn by script and was not read | | Status | https://status.fonoa.com on UptimeRobot with three heartbeat monitors, E-Invoicing, Lookup and Tax | | Capabilities | tax.calculate, tax.transactions, tax.invoicing | | Tags | hosted, paid, closed-source, api-key, openapi, llms-txt, sandbox, webhooks, sales-led, status-page, iso27001 | | JSON | https://www.anchorterminal.com/api/v1/tools/fonoa.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 | 66 | 13.2 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 68 | 11.1 | | Agent ergonomics | 13% | 16.2 | 64 | 10.4 | | Security & auth | 14% | 17.5 | 47 | 8.2 | | Payments & pricing | 10% | 12.5 | 3 | 0.4 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 49 | 4.3 | | Transparency & trust (editorial 27, provenance 69) | 7% | 8.8 | 48 | 4.2 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **51.7 → D** | ### Why each score - Reliability 66: Graded on the public REST API with the hosted lines. status.fonoa.com runs on UptimeRobot with three monitors, E-Invoicing, Lookup and Tax, and 90 days of daily uptime (20). All three show 100 per cent over 90 days and the page's update feed lists nothing in the 30 days to 8 October 2026. The monitors are heartbeats and we read no incident reports older than that feed, so 27 of 30. No rate limit numbers found (0). E-invoicing and onboarding endpoints document a 429 that says to try again a bit later, with no `Retry-After`. Submissions are idempotent by `transaction_id` and the docs say replays are safe (9). No SLA found on the public pages (0). Lookup v2, Tax v2 and E-invoicing v1 carry no beta label, while Instant Lookup is still being rolled out by country (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 68: Each reference page carries an OpenAPI 3.0 definition for its endpoint, readable in the Markdown twin. No single downloadable spec was found (20). docs.fonoa.com/llms.txt indexes every page as Markdown (10). Lookup descriptions state purpose and result states, and e-invoicing guides explain when to adjust, credit or cancel. The calculation endpoint's description covers only its two examples (13). The Lookup definitions carry 29 enums. The e-invoicing definitions carry none, with allowed values in prose and query parameters typed as plain strings (8). Request and response examples on every page read, a page on synchronous and asynchronous errors, and sandbox inputs that trigger each error. The calculation definition lists no 401 or 429 (12). Versions sit in the path, with Lookup v1 beside v2. No changelog was found and docs.fonoa.com/changelog returns 404 (5). - Agent ergonomics 64: List endpoints take `limit`, default 25, with no field selection, and validation results are long (12). Cursor paging with `next_cursor`, 27 query parameters on the transaction list and 14 on the company list. Calculations have no list endpoint (17). 400 responses carry `code`, `message` and `type` with field-level messages, and later failures arrive on the transaction and by webhook. A missing key returns the plain text "Unauthorized" (15). E-invoicing is idempotent by `transaction_id`, a repeat inside one minute returns the same `operation_id`, and webhooks carry a `webhook_id`. Lookup and Tax have no idempotency key (15). A calculation needs few fields. Most work is asynchronous, webhooks are configured by Fonoa staff, and no official SDK was found on npm, PyPI or GitHub (5). - Security & auth 47: One subscription key in the `Ocp-Apim-Subscription-Key` header, issued by Fonoa as a primary and secondary pair, with no scopes or expiry found (20). Separate keys for sandbox and production, and countries enabled per tenant. No read-only key or approval step for cancellations and credits found (5). Returns business names, addresses and tax authority messages written by others, with no injection guidance found (3). A history endpoint lists every operation on a transaction, and the security page mentions a dashboard for user access. No log of API key use found (6). ISO/IEC 27001 badge, a vulnerability disclosure programme with an email address, and third-party penetration tests with reports under NDA. No security.txt or bug bounty, and the Vanta trust centre is drawn by script and was not read (13). Webhooks are signed with an OIDC token that includes a body checksum, noted without points. - Payments & pricing 3: No x402, MPP or L402 (0). No price is published. www.fonoa.com/pricing returns 404 and the site asks visitors to get in touch (0). No free tier or card-free trial found. A sandbox with unlimited usage and a demo environment exist, and a key for either comes from Fonoa after contact, scored as partial (3). Keys are issued by Fonoa staff, so an agent cannot get access on its own (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 49: Closed service with no release tags. The newest reference pages we read, on document templates, were updated on 2 October 2026 per their `updatedAt` field (30). No dated changelog. Page timestamps show edits on 21 July, 29 July and 2 October 2026, and a product updates post covers July 2026 releases (8). Support through a Zendesk request form and a support email address, with no public changelog or community channel found (6). No official SDK, and no server in the official MCP registry (0). No packages to assess. The docs site is current (5). - Transparency & trust 48: Closed service. The only public terms took effect on 14 May 2020, name older seller sites and are governed by Croatian law. The contract for API customers is not published (8). The privacy notice says it does not cover data processed on behalf of customers, gives no retention periods and says data is stored primarily in the EEA. The 2020 terms say issued invoices are stored for up to 18 months. No public DPA found (10). No deprecation policy found. Lookup v1 is documented beside v2 with no end date (3). Storage primarily in the EEA is stated. No subprocessor list was found on the pages read, and the trust centre was not readable (6). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/fonoa.md (JSON https://www.anchorterminal.com/fixes/fonoa.json) ### What we couldn't check - unchecked: the Vanta trust centre at trust.fonoa.com, which is drawn by script. Certifications beyond the ISO/IEC 27001 badge, the subprocessor list and any DPA may be there - unchecked: status history older than the 30 days the page's update feed returned - unchecked: reference pages we did not fetch. 33 of the 64 pages in llms.txt were read, so the newest `updatedAt` date may be later than 2 October 2026 - No terms URL is recorded in provenance. Fonoa publishes no service agreement or API terms for fonoa.com customers, only the 2020 Terms of Service for older seller sites - The privacy notice recorded says it does not apply to customer data Fonoa processes as a processor - Whether rate limits exist per key. The docs define a 429 and give no numbers - Whether the Agents product and its MCP access are available to any customer today. The site labels Agents "Coming soon" - Whether the Returns product has an API. No Returns endpoints appear in the docs, so tax.filing is not claimed - lastRelease is the newest `updatedAt` date on the reference pages read, since Fonoa publishes no API changelog - The batch lead was right on the vendor, URL, docs and interface. It did not say that sandbox and production keys are issued only by Fonoa staff ### Sources - docs index for agents: (seen 2026-10-08) - environments and how keys are obtained: (seen 2026-10-08) - authentication: (seen 2026-10-08) - sandbox environment: (seen 2026-10-08) - Lookup sandbox test inputs: (seen 2026-10-08) - webhooks: (seen 2026-10-08) - errors and warnings: (seen 2026-10-08) - request a validation, Lookup v2: (seen 2026-10-08) - Instant Lookup: (seen 2026-10-08) - request a calculation, guide: (seen 2026-10-08) - request a calculation, reference: (seen 2026-10-08) - commit a calculation: (seen 2026-10-08) - submit a transaction, idempotency: (seen 2026-10-08) - submit a transaction, reference: (seen 2026-10-08) - list transactions: (seen 2026-10-08) - list companies: (seen 2026-10-08) - document templates, updated 2 October 2026: (seen 2026-10-08) - changelog address, 404: (seen 2026-10-08) - status page: (seen 2026-10-08) - status page monitor feed, loaded by the page: (seen 2026-10-08) - status page update feed, loaded by the page: (seen 2026-10-08) - security page: (seen 2026-10-08) - trust centre, not readable: (seen 2026-10-08) - terms of service, 14 May 2020: (seen 2026-10-08) - privacy notice: (seen 2026-10-08) - website llms.txt: (seen 2026-10-08) - Agents product page: (seen 2026-10-08) - pricing address, 404: (seen 2026-10-08) - product updates post: (seen 2026-10-08) - security.txt, 404: (seen 2026-10-08) - unauthenticated API response: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - npm search: (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 69/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Fonoa Technologies Limited | 20/20 | | Domain age | fonoa.com, registered 2004-08-24 (22 years) | 15/15 | | Endpoint on the vendor's domain | api.fonoa.com | 15/15 | | Terms of service | not found | 0/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.fonoa.com | 10/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | The privacy notice names Fonoa Technologies Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, Ireland as data controller. The site footer gives Irish company number 677236. No terms URL is recorded. The only terms Fonoa publishes, at www.fonoa.com/legal/terms-of-service, took effect on 14 May 2020, apply to fonoatech.com, efacturacion.net, efiscal.biz, portugal.fonoatech.com and efatture.net, name Fonoa Technologies ltd. and are governed by Croatian law. No service agreement or API terms for fonoa.com customers were found. The privacy notice says it does not apply to personal data Fonoa processes on behalf of customers using its software, where Fonoa is a processor under the customer's contract. No date of last update was found on the page. The API answers at api.fonoa.com, sandbox.fonoa.com and api-demo.fonoa.com, all on the vendor's domain. www.fonoa.com/.well-known/security.txt and www.fonoa.com/security.txt return 404. The security page describes a vulnerability disclosure programme with an email address. No changelog was found. docs.fonoa.com/changelog returns 404, and product news is published as blog posts. RDAP for fonoa.com gives a registration date of 2004-08-24. ### 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**. We found no terms of service published for this product, so there is nothing to read and the check scores 0. **Privacy policy** (https://www.fonoa.com/legal/privacy-notice), read 2026-10-08, gives no date, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Marketing and advertising partners: We may share limited personal data with selected partners to support the delivery, optimisation, and measurement of our marketing efforts." - Not found in the text. Gives the date it was last updated. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. Gives an email address, hidden from our reader by the page. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). The notice does not cover personal data Fonoa processes for customers inside its software products, where Fonoa is a data processor. "This Privacy Notice does not apply to personal data we process on behalf of our customers when they use our software products." ## Live (updated 2026-10-08 21:53 UTC) - Right now: up, HTTP 404, 68 ms, checked 2026-10-08 21:53 UTC (get on `https://api.fonoa.com`) - Uptime 24h 100.0% (28 probes) · 30 days 100.0% (28 probes) · p50 81 ms · p95 161 ms - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/fonoa.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 - Every reference page is served as Markdown with its OpenAPI 3.0 definition inline, indexed by docs.fonoa.com/llms.txt - E-invoicing submissions are idempotent by `transaction_id`, and the docs say a transaction can be replayed any number of times - The sandbox at sandbox.fonoa.com returns fixed outcomes for documented test inputs, including errors, delays and HTTP 500 - Webhooks carry a signed OIDC token with a SHA-256 checksum of the body, valid for one hour - status.fonoa.com shows 100 per cent over 90 days for its E-Invoicing, Lookup and Tax monitors on 8 October 2026 ## Weaknesses - No self-serve signup. Sandbox, demo and production keys are issued by Fonoa after contact by email or the sales form - No pricing page. www.fonoa.com/pricing returns 404 and the site's buttons read "Get in touch" - No rate limit numbers found. The 429 response says "Try again a bit later" with no `Retry-After` documented - No changelog, deprecation policy, official SDK or MCP server found. docs.fonoa.com/changelog returns 404 - The only public terms took effect on 14 May 2020 and cover older seller sites. They bar benchmarking and automated access without written permission ## Before you call it (notes for agents) 1. Send the key in the `Ocp-Apim-Subscription-Key` header. Use the sandbox key at https://sandbox.fonoa.com and the production key at https://api.fonoa.com 2. Treat validations and e-invoicing submissions as asynchronous. POST, then poll the GET endpoint or wait for the webhook, and avoid tight polling 3. Reuse the same `transaction_id` on a retry of `/v1/transactions`. A transaction already processed is not processed again 4. Commit a calculation with POST `/tax/v2/calculations//commit` only when the sale is final. The commit adds it to revenue tracking 5. Ask the Fonoa contact to configure webhooks. There is no API for it, and always fetch `resource_url` as given in the webhook ## Connect First request: ```bash curl --location 'https://sandbox.fonoa.com/lookup/v2/single-validations' \ --header 'Content-Type: application/json' \ --header 'Ocp-Apim-Subscription-Key: ' \ --data '{ "country_iso_code": "pl", "tax_identification_number": "2000" }' ``` Through letme (picks today, calling later): https://letme.dev/fonoa. 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 | | --- | --- | --- | --- | --- | --- | --- | | Avalara AvaTax | B | 68.8 | 172 | tax.calculate, tax.transactions, tax.invoicing | no | https://www.anchorterminal.com/tools/avalara.md | | Quaderno | C | 59.5 | 427 | tax.calculate, tax.transactions, tax.invoicing | no | https://www.anchorterminal.com/tools/quaderno.md | | Vertex O Series | C | 54.7 | 526 | tax.calculate, tax.transactions, tax.invoicing | no | https://www.anchorterminal.com/tools/vertex-tax.md | | Anrok | C | 61.6 | 361 | tax.calculate, tax.transactions | no | https://www.anchorterminal.com/tools/anrok.md | | Kintsugi | C | 60.7 | 392 | tax.calculate, tax.transactions | no | https://www.anchorterminal.com/tools/kintsugi.md | | TaxJar | C | 57.6 | 470 | tax.calculate, tax.transactions | no | https://www.anchorterminal.com/tools/taxjar.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 API has three product areas, Lookup for tax ID validation (`/lookup/v2`, `/instant-lookup/v1`), Tax for calculation (`/tax/v2/calculations`) and E-invoicing (`/v1/transactions`, `/onboarding/v2`) (source: ) - Three environments are documented, sandbox.fonoa.com with fixed data and unlimited usage, api-demo.fonoa.com with limited usage, and api.fonoa.com for production (source: ) - Fonoa says the Transactions API is idempotent and that a `transaction_id` is processed once only, so a client can replay a submission safely (source: ) - The website lists Agents as "Coming soon" and says AI tools will call it through MCP. No MCP endpoint or MCP documentation was found, and the official MCP registry has no Fonoa server (source: ) - www.fonoa.com/llms.txt carries instructions addressed to AI models on which Fonoa sources to prefer and how not to describe the company. We recorded it and did not act on it (source: ) - The public Terms of Service took effect on 14 May 2020, name fonoatech.com and four other seller sites, and bar benchmarking and access by automated means without written permission (source: ) - The security page shows an ISO/IEC 27001 badge, describes a vulnerability disclosure programme and links a trust centre at trust.fonoa.com (source: ) ## Compare - [Anrok vs Fonoa](https://www.anchorterminal.com/compare/anrok-vs-fonoa.md): C 61.6 vs D 51.7 - [Avalara AvaTax vs Fonoa](https://www.anchorterminal.com/compare/avalara-vs-fonoa.md): B 68.8 vs D 51.7 - [Fonoa vs Kintsugi](https://www.anchorterminal.com/compare/fonoa-vs-kintsugi.md): D 51.7 vs C 60.7 - [Fonoa vs Numeral](https://www.anchorterminal.com/compare/fonoa-vs-numeral.md): D 51.7 vs D 49.3 - [Fonoa vs Quaderno](https://www.anchorterminal.com/compare/fonoa-vs-quaderno.md): D 51.7 vs C 59.5 - [Fonoa vs TaxCloud](https://www.anchorterminal.com/compare/fonoa-vs-taxcloud.md): D 51.7 vs C 57.4 - [Fonoa vs TaxJar](https://www.anchorterminal.com/compare/fonoa-vs-taxjar.md): D 51.7 vs C 57.6 - [Fonoa vs Vertex O Series](https://www.anchorterminal.com/compare/fonoa-vs-vertex-tax.md): D 51.7 vs C 54.7 - [Fonoa vs Zamp](https://www.anchorterminal.com/compare/fonoa-vs-zamp.md): D 51.7 vs D 49.5 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on fonoa.com or one of its subdomains. 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": "fonoa", "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 Fonoa on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Fonoa on Anchor Terminal](https://www.anchorterminal.com/badges/fonoa.svg)](https://www.anchorterminal.com/tools/fonoa) ``` Plain link: ```html Fonoa on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Fonoa 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/fonoa-dark.png - Light: https://www.anchorterminal.com/assets/share/fonoa-light.png