VerseDB Developers Terms

VerseDB Developers ("Developers") is where organizations buy and manage a commercial license to the VerseDB API, at developers.versedb.com: a plan, its API keys, the people on the organization's team, and its billing. VerseDB is operated by Reggio Digital LLC, a North Carolina limited liability company ("VerseDB," "we," "us," or "our").

These Developers Terms add to the VerseDB Terms of Service, which also apply to your use of Developers and the API. Section 12 of the Terms of Service limits the API to non-commercial use unless you hold a license; a plan bought through Developers is that license for as long as its subscription is active. Where the two documents conflict, these Developers Terms control for licensed API use. Section numbers below that name the Terms of Service refer to that document.

An organization can be a company or a single person working on their own. If you use Developers on behalf of a company, you represent that you have the authority to bind it to these Terms, and "you" refers to both you and that company. You accept these Terms on the setup's Terms step, before you subscribe, and by using Developers or a licensed key afterwards. If you do not agree to them, do not use Developers.

The account that sets up an organization is its owner. Only the owner manages the team, billing, and the organization's settings. The owner may invite other VerseDB accounts to join, up to the number of people the plan allows (the owner and open invitations included), and may remove them. Each member needs a VerseDB account in good standing, and every member can make and revoke keys.

A key belongs to the member who made it. When a member leaves or is removed, the keys they made stop working, so replace any key a running service depends on before removing its maker. You are responsible for what the people on your team do with the organization's keys, and for removing a member who should no longer have access.

Plans are billed monthly in advance through Stripe and renew automatically until canceled. The owner can change the plan, update the payment method, and download invoices from the Billing page. A change of plan takes effect at once. Moving to a larger plan charges the prorated difference straight away; moving to a smaller one leaves a prorated credit that is applied to later invoices.

You may cancel at any time. Your keys keep working through the end of the paid period, and no further charges are made. No refunds are given for partial periods, except as Section 9 of these Terms provides or where required by law. If a payment fails, Stripe retries it for a period and your keys keep working meanwhile; if it is still unpaid at the end of that period, the subscription ends and the organization's keys stop working.

We may change plan prices with 30 days' notice to the organization's owner. A price change applies from the first billing period after the notice period ends.

Keep your keys secret. Do not put a key in code that runs on your users' devices or in a public repository; call the API from your own servers. Revoke a key as soon as you think it has been exposed. We may revoke a key that we believe has been exposed or misused.

Each plan allows a set number of keys, and all of an organization's keys share the plan's hourly and daily allowance; more keys add no volume. Requests over the allowance are refused until it refills. Do not create extra organizations or accounts to get around a limit.

While your subscription is active, you may use the data the API returns in your own applications and services, including commercial ones, and display it to your users. Keep what you show accurate.

Credit VerseDB on every page or screen that shows VerseDB data, with the words "Comic book data from VerseDB" (or "Data from VerseDB", or wording that names VerseDB as the source just as clearly) linked to versedb.com. One credit per page or screen is enough, however many records it shows. Place it near the data, in type your users can read, without hiding it behind a click or a tap. The credit must not suggest that VerseDB endorses your product.

Where the data appears somewhere you do not control or that cannot carry a link, such as a listing you publish on another marketplace, a printed label or receipt, or a spoken answer, nothing has to appear there; credit VerseDB instead in your own product where your users work with the data, or on its about or documentation page. Where your service passes VerseDB data to your customers' own applications, they must credit VerseDB in the same way wherever they display it. Data used only inside your organization needs no credit. Any other arrangement needs our written agreement.

You may store the data your applications retrieve for as long as you use it to run them. Refresh each stored record from the API at least once every 30 days, so that corrections made on VerseDB reach your users. You may keep VerseDB's numeric IDs next to your own records for as long as you like.

You may not:

• sell, license, or give away VerseDB data as a dataset or database of its own, or use it to build a database that competes with VerseDB;
• download the catalog in bulk beyond what your applications need, or mirror it;
• share your keys or your access with anyone outside your organization;
• retrieve data in ways the API documentation does not describe, such as scraping versedb.com; or
• use the data in a way that breaks the law or the Terms of Service.

Cover images and other artwork belong to their publishers and creators, and character names and logos to their owners. This license grants no rights in them beyond displaying what the API returns alongside the data it describes.

We remove material from VerseDB when its owner asks us to, under the copyright policy in Section 5 of the Terms of Service. When the API no longer returns a record or image you have stored, or returns it changed, delete or update your copy within 30 days, at your next refresh. If we tell you that something you store has been taken down, delete it within 7 days. Copyright notices about VerseDB go to versedb.com/dmca; a notice about your own application goes to you.

When you set up an organization we keep its name, its website, what you are building, who it is for, and the daily volume you expect. Stripe collects the payment card, billing address, and any tax ID, and we keep the Stripe customer and subscription references. We count each key's requests per hour. These records are stored privately and kept while the organization exists, and after that for as long as we need them for billing, tax, and abuse-prevention records. We use them to run and bill your plan, to answer support requests, to prevent abuse, and as described in our Privacy Policy.

Some Developers features may need our review before they are turned on for an organization. Where one does, we will say so on the feature and may ask for more information about how you will use it.

We may add, change, or retire API endpoints and fields. Changes that break existing requests come in a new version of the API, and we will announce the retirement of an endpoint or version through the API documentation or by email to the organization's owner before it is removed. Do not rely on fields or response shapes the documentation does not describe.

We may suspend or terminate an organization's access to Developers and the API, with or without notice, for breach of these Terms or the Terms of Service, for non-payment, or for use that threatens the stability of VerseDB. A suspended organization's keys stop working, but its subscription keeps running; the owner can still reach the Billing page and cancel it there.

If we suspend or terminate access because of your breach or non-payment, no refund is due. If we end access for any other reason, we refund the unused part of the current paid period.

When access ends, or the subscription ends, your license ends with it. Stop showing VerseDB data in your applications and delete the VerseDB data you stored within 30 days; you may keep VerseDB's numeric IDs. Sections 5, 6, and 10 of these Terms, and Section 9 of the Terms of Service, survive termination to the extent stated in them.

The API and its data are provided as described in Section 9 of the Terms of Service: without warranties, and with the disclaimers and indemnification set out there. Unless your organization has a separate written agreement with us, no uptime or support commitment applies.

To the fullest extent the law allows, VerseDB's total liability arising out of or relating to these Terms, Developers, or the API is limited to the amount your organization paid us for Developers in the 12 months before the event giving rise to the claim. The dispute resolution and arbitration terms in Section 14 of the Terms of Service apply to these Terms.

We may update these Terms from time to time. If we make material changes, we will tell each organization's owner by email or with a notice in Developers, and the changes take effect 30 days after that notice, unless a shorter period is required by law or to address security or fraud risks. The "Last updated" date at the top of this page reflects the most recent revision.

Your continued use of Developers or a licensed key after changes become effective constitutes acceptance of the updated Terms. If you do not agree to them, cancel before they take effect.

If you have any questions about these Terms, or need a plan larger than the ones offered here, please contact us at: