Felo API Platform · SCTA
Disclosure under the Specified Commercial Transactions Act (SCTA)
Business information, service credit purchases, payment and refund policy for Felo API Platform.
Last updated:
- Business operator
- Felo株式会社
- Address
- 10F, Shin-Marunouchi Building, 1-5-1 Marunouchi, Chiyoda-ku, Tokyo 100-6510, Japan
- Telephone
- 03-6826-9985
- [email protected]
- Responsible person
- 司馬雲瑞
- Website
- Felo API Platform
- Service and pricing
- Prepaid service credits for model APIs and Data APIs, starting at USD 1. No subscription is required. Credits are denominated in USD and used to pay for actual API usage; they are not a cash deposit or withdrawable balance. Current rates are shown on the pricing page. The amount payable and any applicable taxes are shown at checkout.View pricing
- Additional charges
- No shipping, account-opening or subscription fees. Internet connection charges and any currency conversion or payment fees charged by your bank or payment provider are your responsibility.
- Payment methods and timing
- Use a payment method available in Console checkout. Available methods depend on your region and the checkout page. Payment is made when purchasing credits; API usage charges are deducted from credited service credits.
- Service availability
- Service credits become available after payment is confirmed and credited to your account. API use requires an account, an API key and sufficient credits, and is subject to current service availability.
- Cancellation and refunds
- Completed top-ups credited to your account are non-refundable, including unused credits, except where mandatory applicable law requires otherwise. Credits cannot be withdrawn or exchanged for cash. You may stop using the service at any time; stopping use does not entitle you to a refund. Contact support to investigate and correct payment or billing errors.API supplemental terms
- System requirements
- Use an up-to-date web browser and an internet connection to access Console. API integrations require an environment capable of HTTPS requests and the requirements stated in the API documentation.