ByT5's architecture is based on the T5v1.1 model, refer to T5v1.1's documentation page for the API reference. They
only differ in how inputs should be prepared for the model, see the code examples below.

Since ByT5 was pre-trained unsupervisedly, there's no real advantage to using a task prefix during single-task
fine-tuning. If you are doing multi-task fine-tuning, you should use a prefix.
Usage example
ByT5 works on raw UTF-8 bytes, so it can be used without a tokenizer:
thon