# Cloud and institutional marketplace listing packet Prepared 7 October 2026 for **LIQUILENS PRIVATE LIMITED**, public brand **LiquiLens**. This is submission material, not evidence of vendor approval. The public research service and individual product APIs already exist. Cloud seller onboarding, commercial delivery and native platform acceptance remain separate work. ## Reusable product information | Field | Prepared value | | --- | --- | | Product title | Financial Evidence Research Desk | | Publisher | LIQUILENS PRIVATE LIMITED | | Product type | Read-only financial research software and MCP tools | | Suggested SKU | financial-evidence-research-desk | | Demonstration | https://beepboop2025.github.io/financial-evidence-skills/start/ | | Documentation | https://beepboop2025.github.io/financial-evidence-skills/api/ | | OpenAPI | https://beepboop2025.github.io/financial-evidence-skills/api/openapi.json | | REST base | https://api.seiche.info/openbb | | Research MCP | https://api.seiche.info/openbb/mcp | | Source router MCP | https://liquilens.in/mcp/financial-evidence | | Support | mrinal@liquilens.in | | Support page | https://beepboop2025.github.io/financial-evidence-skills/support/ | | Privacy | https://beepboop2025.github.io/financial-evidence-skills/privacy/ | | Terms | https://beepboop2025.github.io/financial-evidence-skills/terms/ | | Public logo source | https://raw.githubusercontent.com/beepboop2025/financial-evidence-skills/v0.1.6/assets/logo-400.png | | Source status | https://api.seiche.info/openbb/api/v1/sources | | Deployment identity | https://api.seiche.info/openbb/api/v1/release | **Short description:** Read-only tools for source-cited bank, funding and market-liquidity research. Query seven dataset views through a browser, REST or MCP while preserving observation dates, units and unavailable values. **Long description:** Financial Evidence Research Desk brings public financial evidence into analysts' existing research tools. Its browser desk, typed REST interface and eight-tool MCP service support covered-bank disclosures, money-market benchmarks and history, capital-market context, liquidity evidence and source-health checks. The service connects the LiquiLens, Seiche, Undertow and Palimpsest research surfaces. Results retain source links, observation dates, native units and unavailable states. Coverage varies by source and dataset; the China view may contain availability information only. A successful request is not proof that every observation is current. Public reads require no account or API key. CSV, notebook, spreadsheet and API-client examples help reviewers reproduce a bounded research task. The software does not execute trades or provide executable quotes or credit ratings. Software licensing and permission to redistribute underlying data are separate. Any commercial data offering must define its permitted sources, customer rights, update cadence and support commitments before publication. **Three highlights:** 1. Retrieve cited evidence without losing dates, units or missingness. 2. Use seven bounded dataset views through REST, MCP or a browser desk. 3. Reproduce a research task with documented examples and inspect source health. **Suggested categories:** Financial Services, Data Analysis, Research. **Keywords:** financial research, bank disclosures, funding markets, liquidity, source provenance, MCP, OpenAPI. **Claims to leave unfilled:** customer count, monthly active people, customer logos, certifications, contractual uptime, commercial redistribution rights and vendor endorsements. None is established by a marketplace listing. ## Amazon: choose the correct channel ### AWS Marketplace API-based AI agents and tools The relevant offering is an **MCP tool**, using the SaaS API-based listing wizard. The seller portal was opened and reached AWS sign-in; no authenticated seller account or product draft was verified. The prepared public logo still needs a seller-controlled S3 asset. Choose fulfillment and commercial terms only after the intended offer is defined. AWS documents its product metadata, fulfillment choices and review steps in the [listing guide](https://docs.aws.amazon.com/marketplace/latest/userguide/listing-saas-ai-agents.html). The existing anonymous MCP endpoint is a working demonstration. A subscribed commercial offering needs the selected AWS fulfillment flow, customer entitlement, usable credentials, cancellation/revocation and integration tests. Optional research-measurement keys do not implement those functions. See the [integration requirements](https://docs.aws.amazon.com/marketplace/latest/userguide/integrating-api-ai-agents-tools.html). | Remaining item | Concrete completion evidence | | --- | --- | | Seller identity and account | Registered company profile and approved seller status | | Regional selling route | Confirmed buyer geography and supported commercial arrangement | | Offer and rights | Defined product, source permissions, price, EULA, refund and support terms | | Fulfillment | Tested AWS subscription-to-entitlement and credential lifecycle | | Listing assets | S3 logo, support resources, product metadata and final screenshots | | Vendor review | AWS submission receipt, approval and independently accessible product URL | The India-specific seller route requires a separate account and currently limits that route to Indian buyers. Its tax and banking declarations must use verified company records. Do not assume it provides worldwide sales merely because the website is global. [AWS India seller FAQ](https://docs.aws.amazon.com/marketplace/latest/userguide/india-seller-faq.html). ### AWS Data Exchange This is a distinct data-product route. Start with one source-approved dataset and a data dictionary, cadence, revision policy, sample and customer license. The API asset path requires an eligible public **Amazon API Gateway REST API** and the documented authorization setup; our externally hosted URL alone is not that asset. [API data-grant requirements](https://docs.aws.amazon.com/data-exchange/latest/userguide/creating-a-data-grant-api.html). Source eligibility and redistribution approval precede an upload. A public source URL does not automatically grant a commercial data license. [Providing datasets](https://docs.aws.amazon.com/data-exchange/latest/userguide/providing-data-sets.html). ### Other Amazon routes - A container offer needs a separately validated AWS-compatible package and its own offer lifecycle; an existing GHCR image does not establish a listing. [AgentCore container requirements](https://docs.aws.amazon.com/marketplace/latest/userguide/bedrock-agentcore-runtime.html). - Amazon Appstore needs an actual supported device application. General Android-device distribution ended in 2025; Fire-device support continues. There is no such application in this submission packet. [Amazon's platform notice](https://developer.amazon.com/apps-and-games/blogs/2025/02/upcoming-changes-to-amazon-appstore-for-android-devices-and-coins-program). - The Selling Partner Appstore is for applications serving Amazon sellers and vendors through SP-API. Our financial research API has no such native workflow. [SP-API onboarding](https://developer-docs.amazon.com/sp-api/docs/onboarding-overview). ## Other cloud platforms | Destination | Suitable first offer | Work still required | | --- | --- | --- | | Microsoft Marketplace | A SaaS **Contact me** listing for an evaluated research integration | Publisher account, identity, category fit, listing media and certification. This route has fewer technical integration requirements than transactable SaaS. | | Google Cloud Marketplace | A supported SaaS solution with a defined deployment and commercial model | Partner onboarding, business review and the applicable Google Cloud deployment/billing requirements. Existing external hosting is not proof of eligibility. | | Snowflake Marketplace | A rights-approved dataset share or native application | Provider profile, Snowflake artifact, sample queries, data dictionary, account privileges and review. | | Databricks Marketplace | A defined dataset delivered using the supported sharing route | Eligible account, Unity Catalog workspace, provider profile, permissions, policies and review. | Primary requirements: [Microsoft SaaS planning](https://learn.microsoft.com/en-us/partner-center/marketplace-offers/plan-saas-offer), [Google Cloud onboarding](https://docs.cloud.google.com/marketplace/docs/partners/get-started), [Snowflake publication](https://docs.snowflake.com/en/collaboration/provider-listings-creating-publishing), [Databricks provider setup](https://docs.databricks.com/aws/en/marketplace/become-provider). ## Institutional platforms Use the [platform evaluation brief](../partners/partner-brief.md) and its bounded pilot, together with the API contract and source-status endpoint. - **Bloomberg App Portal/BQuant:** establish the current developer admission route and an entitled development sponsor, then test the native workflow. The [App Portal developer brochure](https://assets.bbhub.io/professional/sites/10/App-Portal-Overview-for-Developers.pdf) is historical; it is not a current submission receipt. - **LSEG Workspace:** use the [business partnership route](https://www.lseg.com/en/about-us/business-partnerships-marketplace/partners-portal) to confirm the supported solution/content integration and commercial terms. - **FactSet:** confirm current provider admission, delivery format and source permissions; the [provider brochure](https://go.factset.com/hubfs/Website/Resources%20Section/Brochures/benefits-of-becoming-an-open-factset-marketplace-partner-brochure.pdf) is background material rather than proof of present eligibility. - **Reuters Connect:** its [content partnership route](https://reutersagency.com/solutions/content-distribution/) is for licensable editorial content. An original research-content product would need separate rights and editorial review; it is not a generic financial-terminal API directory. - **Nasdaq Data Link and BattleFin:** qualify the dataset, rights, delivery and commercial fit before a provider application. No acceptance is claimed. ## ApyHub prepared provider profile An authenticated Starter workspace was reached through the operator's GitHub account using read-only profile/email permissions. The prepared provider display name is **LIQUILENS PRIVATE LIMITED**, proposed slug `liquilens`, country India. The account's existing workspace display name was preserved. The provider agreement remains **unsigned**. Its v1.1 terms require a response to escalated support within 24 hours, representations about software/data rights, and restrictions on soliciting marketplace customers. The displayed economics are USD 0.000025 per atom, a USD 100 payout threshold and monthly settlement subject to the agreement. Provider profile preparation is not an API listing. [Provider terms](https://apyhub.com/provider-terms). Before proceeding, define the exact data scope and support owner, review the commercial agreement, and obtain company authorization to accept those commitments. No API, pricing plan or paid entitlement was published in this workspace by this packet. ## Acceptance and adoption Retain submission receipts and then verify the public listing independently. Track completed research tasks, returning people and 30-day active people separately from directory visits, crawlers, install-button clicks and API calls. The objective is one million monthly people using the products; this packet does not establish current MAU or a guaranteed acquisition outcome.