English-Corpora.org

English-Corpora.org

 
For administrators

Frequently asked questions

For end users

Other information


Questions: admin@english-corpora.org

 

API key (university)

One challenge with academic licenses is how to make it so that individual users at the university don't have to pay for their own AI/LLM use. First, let's discuss what are four possible solutions -- none of which is very good.

1. One option might be to have the payment for academic license cover the cost of AI/LLM access for all users at the university. But suppose that there are 500 users from a university, and each person does an average of just 40-50 AI-based queries each month. After a year, that would be 300,000 queries (500 x 50 x 12). If English-Corpora.org had to pay for all of that API access itself, it would actually lose money for the academic licenses for some universities.

2. But it also doesn't make much sense for a university to pay a "surcharge" ahead of time, which could be used by anyone from the university, since a handful of people might use up all of those AI credits themselves, and leave nothing for others.

3. It also doesn't make sense to have a university pay for the API queries "after the fact" -- after users at their universities have incurred charges for their API access. What if the university can't/won't pay at that time, or if there are "bureaucratic hurdles" in paying for the AI/LLM use?

4. The last (not good) option is to have individuals pay for their own "AI credits". But that would be a change from the past, where everything was paid for by the university.


We feel that the best option is let corpus users take advantage of the university's API key (if available) for a particular LLM (OpenAI, Google, Anthropic, etc). Here's how it works:

1. Via the "management console" for their license, the university puts in the API key for the LLM (and they can do this for multiple LLMs, if they want). Note that this API key is encrypted -- neither the individual users nor the corpus administrators can see it.

2. When authenticated users from the university select their default LLM(s), they will see that their university has already entered the API key for a particular LLM, and they can select that LLM as their default. Again, they will never see the API key itself, but rather just the fact that the university has put in an API key.

3. All LLM use is logged, even at the level of individual API calls (including the number of tokens sent and received). Universities can access at any time a "report" of the usage via their API key, either by date or by user.

We believe that this solution will meet the needs of English-Corpora.org, the universities that have academic licenses for the corpora, and the individual users from these universities.